-
Notifications
You must be signed in to change notification settings - Fork 20
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
Fork in sidechain block production #1524
Comments
Another observation is sometimes a sidechain block is broadcasted to the same peer multiple times:
As a result, only the first block import was successful, the subsequent import was rejected with |
The problem started with block worker0 successfully produced
worker1 tried to produce
before that it already synced to parentchain block
Then it tried to import the block
block
As a result, they were not in sync any more and started producing their own versions of blocks. e.g. for the problematic
For the following blocks from worker0, worker1 found it was already imported and thus ignored it, e.g. for
|
❗ This issue is stale because it has been open for 60 days with no activity. |
Note: when tackling this; let's try reenabling the skipped tests in |
Redundant broadcasting should be resolved in #1546 |
Context
It happened once on the staging, two workers diverged in the end.
Many
Consensus(BlockAncestryMismatch
errors in worker0 logs, meaning that the imported blocks (most likely produced by worker1) don't follow the already knownlast_block
locally. As a result, the blocks will be discarded.So it seems worker1 is producing blocks at a higher speed than worker0.
Tasks:
Logs (only workers):
log.tar.gz
✔️ Please set appropriate labels and assignees if applicable.
The text was updated successfully, but these errors were encountered: