-
Notifications
You must be signed in to change notification settings - Fork 98
[Bifrost] LogChainExtender is managed by watchdog #3598
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
Conversation
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.
Thanks for simplifying the overall structure by letting the watchdog manage the LogChainExtender. LGTM. +1 for merging :-)
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.
+1 to merge fwiw, this is definitely cleaner! 🐕 Thank you, @AhmedSoliman!
// ignore in-flight trims if task-center is shutting down. | ||
// we don't want to prematurely shutdown the watchdog as we | ||
// might need it to continue running "during" shutdown. |
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.
This is a nice touch!
The PR introduces two changes: - `Bifrost::find_tail()` will only attempt to seal the chain if FindTailOpts asks for consistent result; we don't need to cripple the fast path for find-tail. - Find tail will eagerly seal the chain without grace period. This is to avoid unnecessary startup delays for single-node setups. The fact that chain sealing is idempotent makes it lighterweight to perform as it'll coalesce nicely with other reconfigurations that might be happening concurrently.
Allows the system to capture the "source" and the "node" for chain seal markers. There is also a new `--reason` flag to `restatectl log seal` to specify the reason, and the reason + the node id will be printed in `restatectl logs describe <id>` output.
A partial seal is when the tail loglet is sealed but the chain itself is not. The read stream will detect this situation and seal the chain after a grace period (5s+50% jitter).
Stack created with Sapling. Best reviewed with ReviewStack.