-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
TxMgr: Rearrange TxMgr closure in Batcher #9205
Conversation
WalkthroughWalkthroughThe update improves the Changes
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
excited to test this in action ✨
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hopefully this fixes flakes
692f6ad
to
1abba7f
Compare
Moves the
TxManager.Close
to be the first inBatcherService.Close
.This is done because the TxManager now aggressively shuts down work when in the Close state, and declines new work, leading to a faster shutdown of the component. However,
BatcherService
was treatingTxManager
too gently, waiting for work to be finished before ever asking it to shut down.The end result was that the Batcher did not benefit from the faster Closure of TxManager.
By making TxManager closure the first call, any component which awaits TxManager completion will be satisfied much sooner.
Testing
Not tested besides auto-checks here in the PR.