fix: slow L3 sequencer to 333ms to avoid msgIdx race#25
Merged
Conversation
douglance
force-pushed
the
fix/l3-sequencer-block-speed
branch
from
9fba842 to
e226434
Compare
douglance
changed the title
The L3 nitro sequencer ran with execution.sequencer.max-block-speed=100ms. Under load the consensus/execution message index momentarily diverges and nitro's TransactionStreamer rejects eth_sendRawTransaction with "wrong msgIdx got X expected Y" (JSON-RPC -32000), hanging chain-sdk tests and crashing arbitrum-portal E2E setup on the L3 node. Make 333ms the default L3 sequencer max-block-speed in patchGeneratedL3NodeConfig to widen the block-production cycle and shrink the race window. L2 is unchanged (still 100ms; it has timeboost).
douglance
force-pushed
the
fix/l3-sequencer-block-speed
branch
from
e226434 to
544ba3f
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The L3 sequencer runs at
max-block-speed=100ms. Under load the consensus/execution message index diverges and nitro rejectseth_sendRawTransactionwithwrong msgIdx got X expected Y(-32000), hanging chain-sdk tests and crashing arbitrum-portal E2E setup on the L3 node.Make 333ms the default L3 sequencer max-block-speed to widen the block-production cycle and shrink the race window. L2 is unchanged (100ms).