mempool: waitSync channel to block broadcast routines #1386
Conversation
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
3 tasks
f655c50 to
fc1b63c
Compare
hvanz
approved these changes
Sep 22, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Proposal to address synchronization issues of #1119:
broadcastTxRoutineis started for every peer added to the reactor, regardless the output ofWaitSync()broadcastTxRoutinestarts by checking the output ofWaitSync(). If it is true, it blocks on a newwaitSyncChchannel until the node is allowed to broadcast transactions.EnableInOutTxs()method does not startbroadcastTxRoutineinstances any longer, as they are started byAddPeer(). It instead unblocks every blocked routine by closing thewaitSyncChchannel.