Description
Leif Hedstrom 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 Leif Hedstrom, 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.
Attachments
Issue Links
- is related to
-
TS-3622 Writer doing unbounded retries for write VC to be closed during read_while_writer scenario
-
- Closed
-