Repository navigation
test(two-node-sim): model F26, the takeover waiting for a history read in flight on a frozen peer's JM - #1508
Merged
Merged
Conversation
…d in flight on a frozen peer's JM Bed c12b/02c-r1 (image with ultra #219 incl. F25): intermittent 7 s client stall, 0 IO errors. The survivor's JC reader had a history read in flight on the peer's JM when the peer froze; F21 only keeps that JM from being chosen again, the read itself waited for the 8 s NVMe IO timeout and the takeover's reader restart with it. - simnode: CAP_READER_RESETS_PEER_JM_READ (ultra #219, F26 commit) - actors: under the condition reader_read_inflight_on_peer_jm, a solo takeover with F21's capability but not F26's waits until min(freeze + NVME_TIMEOUT, peer's frozen_until), violation "F26" - scenarios: F26-takeover-read-inflight-on-peer-jm, judged on the client stall; F26's capability added to every pending-fix set that includes F25's - test_f26_needs_its_own_fix Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Bed c12b/02c-r1 (image tn2-r12b with ultra #219 incl. F25) hit an intermittent 7 s client stall with 0 IO errors. When the peer froze, the survivor's JC reader already had a history read in flight on the peer's JM. F21 only stops that JM from being chosen as the next source. The read itself waited for the 8 s NVMe IO timeout, and the takeover's reader restart waited with it.
simnode:CAP_READER_RESETS_PEER_JM_READ(the F26 commit on ultra Adding lvol id to lvol events #219, afad24a8).actors: under the new conditionreader_read_inflight_on_peer_jm, a solo takeover that has F21's capability but not F26's waits untilmin(freeze + NVME_TIMEOUT, peer.frozen_until). Violation "F26".scenarios:F26-takeover-read-inflight-on-peer-jm(hang sn2 8 s), judged on the client stall.test_f26_needs_its_own_fix: with all of Adding lvol id to lvol events #219's capabilities except F26's, the scenario fails on F26 only (not on F21, F24 or F25).Test only; no product code changes.
🤖 Generated with Claude Code