[ https://issues.apache.org/jira/browse/TS-3767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Leif Hedstrom updated TS-3767: ------------------------------ Fix Version/s: (was: 6.1.0) 6.0.0 > More unbounded retries within read-while-writer breaking loop detection. > ------------------------------------------------------------------------ > > Key: TS-3767 > URL: https://issues.apache.org/jira/browse/TS-3767 > Project: Traffic Server > Issue Type: Bug > Components: Cache > Reporter: Sudheer Vinukonda > Assignee: Sudheer Vinukonda > Labels: A > Fix For: 6.0.0 > > > [~zwoop] noticed the loop detection (request to self) fails with default > settings, when read-while-writer functionality is enabled. Upon further > investigation, this seems to be caused by more cases of unbounded retries > within read-while-writer (similar to TS-3622), which prevent reaching the > loop detection point (currently, done after the cache lookup state). > TS-3622 added a bound for read-while-writer in the case, where the writer > lock is available, but, the first fragment is not downloaded yet, but, there > are more cases which cause similar issues. > Discussing with [~zwoop], we think we should add bounds in all such cases > with configurable timer (duration) and configurable max number of retries. > Also, refer TS-3768 for a future improvement on this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)