Collator protocol revamp: Change collation hold-off timing to start at leaf activation#11046
Collator protocol revamp: Change collation hold-off timing to start at leaf activation#11046
Conversation
|
Hey @mchristou |
|
Hey @tdimitrov |
tdimitrov
left a comment
There was a problem hiding this comment.
Good job @mchristou. Just a few more nits.
I really like that you've added comments and updated the relevant tests.
'Late advertisement' is not an appropriate term in this case so I made some suggestions to remove it.
An advertisement which is received after the delay timer (300ms) is not necessary late since producing a collation is kind of expensive operation.
...adot/node/network/collator-protocol/src/validator_side_experimental/collation_manager/mod.rs
Outdated
Show resolved
Hide resolved
...adot/node/network/collator-protocol/src/validator_side_experimental/collation_manager/mod.rs
Outdated
Show resolved
Hide resolved
...adot/node/network/collator-protocol/src/validator_side_experimental/collation_manager/mod.rs
Outdated
Show resolved
Hide resolved
...adot/node/network/collator-protocol/src/validator_side_experimental/collation_manager/mod.rs
Outdated
Show resolved
Hide resolved
...adot/node/network/collator-protocol/src/validator_side_experimental/collation_manager/mod.rs
Outdated
Show resolved
Hide resolved
|
/cmd prdoc --audience node_dev --bump patch |
…e_dev --bump patch'
|
The next steps to get the PR merged is to write a PRDoc. This is a short description of the PR + list of the changed crates with the corresponding semver change. We use this for for release notes generation. I've triggered the bot to generate a boilerplate prdoc file for you with |
sandreim
left a comment
There was a problem hiding this comment.
LGTM! Nice work @mchristou
…t leaf activation (#11046) #11022 The hold-off delay should be measured from when the relay parent (leaf) is activated, not when the advertisement message arrives. This prevents artificially delaying messages that already arrived late. ## Changes - Calculate remaining hold-off time from leaf activation, not message arrival - Process immediately if hold-off window has already elapsed - Add test to ensure late-arriving collations skip artificial delay --------- Co-authored-by: cmd[bot] <41898282+github-actions[bot]@users.noreply.github.com> (cherry picked from commit 7beff9b)
|
Successfully created backport PR for |
Backport #11046 into `stable2603` from mchristou. See the [documentation](https://github.com/paritytech/polkadot-sdk/blob/master/docs/BACKPORT.md) on how to use this bot. <!-- # To be used by other automation, do not modify: original-pr-number: #${pull_number} --> Co-authored-by: Marios <marios@parity.io> Co-authored-by: cmd[bot] <41898282+github-actions[bot]@users.noreply.github.com>
#11022
The hold-off delay should be measured from when the relay parent (leaf) is activated, not when the advertisement message arrives. This prevents artificially delaying messages that already arrived late.
Changes