Repository navigation
Retry taking over the history DB instead of staying disabled (v0.14.1) - #3
Closed
Robbie1977 wants to merge 1 commit into
Closed
Robbie1977 wants to merge 1 commit into
Robbie1977 wants to merge 1 commit into
Conversation
When the history lock is held by the previous container during a start-first upgrade, wait and retry every HISTORY_RETRY_SECONDS (default 120) rather than running without history until the next restart. The page shows the reason history is off. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011bFcTBicKxGKtvg89shb6M
Contributor
Author
|
Closing unmerged: this fixed a Cattle-era overlap (Rancher start-first upgrade left the old container holding the history lock). vfb-status now runs on the k8s cluster with one replica, |
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.
If the history lock is held by the previous container during a Rancher start-first upgrade, history used to stay off until the next restart. It now retries every
HISTORY_RETRY_SECONDS(default 120, 0 = never) and enables itself once the lock is free. The page shows why history is off. Unwritable/datais retried too.Tested with two History instances on one file: second is blocked,
retry_open()fails while the first holds the lock and succeeds after release.🤖 Generated with Claude Code
https://claude.ai/code/session_011bFcTBicKxGKtvg89shb6M