Add fixes around fail_action 5#12845
Merged
ezelkow1 merged 6 commits intoapache:masterfrom Feb 2, 2026
Merged
Conversation
added 2 commits
January 30, 2026 16:26
add fixes around read_retry write fail action 5
added 2 commits
January 30, 2026 18:10
Member
Author
|
[approve ci autest] |
bneradt
requested changes
Feb 2, 2026
bneradt
requested changes
Feb 2, 2026
bneradt
requested changes
Feb 2, 2026
bneradt
approved these changes
Feb 2, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
This pull request adds fixes for cache fail_action 5 (READ_RETRY mode) to prevent infinite looping scenarios and handle redirect edge cases correctly.
Changes:
- Prevents looping when read retries are exhausted by bypassing cache instead of attempting another write lock
- Adds defensive check for redirect scenarios with
redirect_use_orig_cache_keyenabled - Adds comprehensive autotests to verify READ_RETRY mode stability and request collapsing
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| src/proxy/http/HttpTransact.cc | Adds two checks to prevent looping in READ_RETRY state: one in HandleCacheOpenReadMiss and a defensive check in set_cache_prepare_write_action_for_new_request for redirect scenarios |
| tests/gold_tests/cache/replay/cache-read-retry.replay.yaml | New test file that validates READ_RETRY mode with concurrent requests, slow origin responses, and verifies request collapsing and system stability |
| tests/gold_tests/cache/cache-read-retry-mode.test.py | Test runner for the READ_RETRY mode test |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
bryancall
pushed a commit
to bryancall/trafficserver
that referenced
this pull request
Mar 16, 2026
Add autest for fail action 5 cache read retry mode add fixes around read_retry write fail action 5
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.
This adds some fixes around fail_action 5. First it prevents a possible looping scenario, previously after exhausting waiting for a read lock after having failed in a write lock it would loop back around to check for write again. Now it will just go to origin. While this allows an extra request through it can prevent some odd scenarios, including one where it just writes back to the cache again anyway which would already be useless. Also if the original rww request is very slow then this allows waiters to bypass it.
Second there could be an issue around redirects, normally a redirect is fine since it would have a different cachekey but if we enable use_orig then we could end up in the same looping contention in that scenario as well.
Also adds some autests, though we should keep an eye on these since they could be timing dependent. So if we start getting failures we can turn them off.