Skip to content

Synchronizer to prune all requests#677

Merged
HagarMeir merged 1 commit intohyperledger:mainfrom
tock-ibm:synch-prune-config-as-well
Mar 15, 2026
Merged

Synchronizer to prune all requests#677
HagarMeir merged 1 commit intohyperledger:mainfrom
tock-ibm:synch-prune-config-as-well

Conversation

@tock-ibm
Copy link
Contributor

A batch of requests with a config change needs to be pruned as well, otherwise the config request and request that co-locate to the sam batch will remain in the mempool.

Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the consensus synchronizer’s catch-up path to prune committed requests from the SmartBFT request pool even when the committed decision includes a config change, preventing config-related batches from leaving stale entries behind in the mempool.

Changes:

  • Always deserialize the proposal payload into a request batch during sync, regardless of whether the decision includes a config block.
  • Prune every request in the committed batch from the mempool, including config requests.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@tock-ibm tock-ibm force-pushed the synch-prune-config-as-well branch from c14f242 to 1f8d3de Compare March 12, 2026 15:26
HagarMeir
HagarMeir previously approved these changes Mar 12, 2026
@HagarMeir HagarMeir dismissed their stale review March 12, 2026 21:09

waiting for tests to pass

A batch of requests with a config change needs to be pruned as well, otherwise the config request and request that co-locate to the sam batch will remain in the mempool.

Signed-off-by: Yoav Tock <tock@il.ibm.com>
@tock-ibm tock-ibm force-pushed the synch-prune-config-as-well branch from 1f8d3de to 2617d53 Compare March 15, 2026 09:37
@HagarMeir HagarMeir merged commit b066a2d into hyperledger:main Mar 15, 2026
9 of 10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants