You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Sudheer Vinukonda (JIRA)" <ji...@apache.org> on 2015/07/14 18:23:04 UTC

[jira] [Created] (TS-3767) More unbounded retries within read-while-writer.

Sudheer Vinukonda created TS-3767:
-------------------------------------

             Summary: More unbounded retries within read-while-writer.
                 Key: TS-3767
                 URL: https://issues.apache.org/jira/browse/TS-3767
             Project: Traffic Server
          Issue Type: Bug
          Components: Cache
            Reporter: Sudheer Vinukonda


[~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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)