Skip to content
This repository has been archived by the owner on Nov 15, 2023. It is now read-only.

Find and fix any subsystem cycles via Versi #5460

Closed
eskimor opened this issue May 5, 2022 · 2 comments
Closed

Find and fix any subsystem cycles via Versi #5460

eskimor opened this issue May 5, 2022 · 2 comments
Labels
T5-parachains_protocol This PR/Issue is related to Parachains features and protocol changes.

Comments

@eskimor
Copy link
Member

eskimor commented May 5, 2022

Based on this we can deploy nodes to some validator group on Versi with a reduced message channel size in order to provoke blocking.

Once nodes stall because of a deadlock - debug & find the cycle (see node stall in the knowledge share section). Continue until nodes are not stalling any more, even with very small message queues.

Once all cycles are found and fixed, we should deploy a reduced channel size (e.g. 100) to all nodes on Versi and leave it like that. This way, if we accidentally introduce a cycle it should be very likely be detected on Versi already. Also consider using a reduced channel size in at least some Zombienet tests.

@eskimor
Copy link
Member Author

eskimor commented May 9, 2022

A first deployment with channel size of 128 did not reveal any new dead locks. A further reduction should be tried as well.

@sandreim
Copy link
Contributor

implemented a compile time solution in #5614.

@ordian ordian added the T5-parachains_protocol This PR/Issue is related to Parachains features and protocol changes. label Aug 16, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
T5-parachains_protocol This PR/Issue is related to Parachains features and protocol changes.
Projects
No open projects
Status: Done
Development

No branches or pull requests

3 participants