Shut down ReplicationWorker and Auditor on non-recoverable ZK error#3374
Merged
Conversation
hangc0276
pushed a commit
to hangc0276/bookkeeper
that referenced
this pull request
Nov 5, 2022
…pache#3374) (cherry picked from commit c3706e9)
hangc0276
pushed a commit
to hangc0276/bookkeeper
that referenced
this pull request
Nov 7, 2022
…pache#3374) (cherry picked from commit c3706e9)
nicoloboschi
pushed a commit
to datastax/bookkeeper
that referenced
this pull request
Jan 11, 2023
…pache#3374) (cherry picked from commit c3706e9) (cherry picked from commit 8ce6538)
Ghatage
pushed a commit
to sijie/bookkeeper
that referenced
this pull request
Jul 12, 2024
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
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.
Descriptions of the changes in this PR:
Shut down Replication Worker and Auditor on non-recoverable ZK error
Motivation
Some errors require one to re-create Zk client.
Currently BK and underlying components cannot do that transparently.
When running AutoRecovery as a separate service it does not seem to crash in such cases and keeps on running while unable to do anything useful and requires operator restarting the service manually.
One can see such log messages like
and other similar
Changes
Now Replication Worker and Auditor will shut down on such errors making their error state visible / letting k8s or service monitor restart them.
Added tests.
Removed KeeperException from some interfaces/implementations to prevent raw ZK exception sneaking through but there are other interfaces, see #3373