Repository navigation
Tail probe: timeout retry + non-alarming logging - #15
Merged
Merged
Conversation
…ubled timeout; log unconfirmed flags as warn
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
2 participants
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.
Root cause of the 22-23 Sep false positives (IASIP S13, Ghosts, Rob & Romesh, Taskmaster): the tail probe's 15s timeout expires under CPU contention and was treated as corruption evidence, triggering a ~5min full-decode confirm per false flag. Now: killed probe retries once with doubled timeout (runTailDecode); if still timing out it routes to the confirm pass as before, but the unconfirmed flag logs at WARN ('tail probe flagged ... running confirm decode') instead of 'ERROR: Corrupt episode detected', so log sweeps stop counting pending confirms as corruption. Real corruption path unchanged.