Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Block propagation failure/partition and node crash #2030

Closed
jondubois opened this issue May 15, 2018 · 1 comment
Closed

Block propagation failure/partition and node crash #2030

jondubois opened this issue May 15, 2018 · 1 comment

Comments

@jondubois
Copy link
Contributor

Expected behavior

Blocks should propagate across the network.
Also, if the socket is no longer attached to a peer object, then we should not call emit on that socket.

Actual behavior

There was a fork in the latest betanet because some blocks were not reaching some nodes. We thought it was a broadhash broadcasting issue initially but it appears be related to this issue LiskArchive/wamp-socket-cluster#35

Steps to reproduce

Run on latest code on betanet with 250 nodes.

Which version(s) does this affect? (Environment, OS, etc...)

Beta 7.4

@jondubois jondubois changed the title Block propagation failure/partition + node crash Block propagation failure/partition and node crash May 15, 2018
@karmacoma karmacoma added this to the Version 1.0.0-beta.7 milestone May 20, 2018
@jondubois
Copy link
Contributor Author

After several rounds of beta testing, this issue has been broken down into smaller chunks:

Note that #2025 has been abandoned in favour of #2042 above.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants