ndncatchunks terminates without receiving every data chunk
This occurs when it will erroneously recount a duplicated chuck. Thus the count will be off and the number of not received chunks is proportional to the number of duplicates recounted.
I wrote a script that will automatically check for this pattern:
Segment #1097 was erroneously retransmitted after it was received! Segment #1096 was erroneously retransmitted after it was received! Segment #1095 was erroneously retransmitted after it was received! Segment #2325 was never received! Segment #2326 was never received! Segment #2327 was never received! Only 2325 out of 2328 segments were received!
As you can see, three segments were recounted causing three segments to never be received.
Updated by Davide Pesavento over 2 years ago
- Assignee set to Ryan Wickman
- Start date deleted (
Ryan Wickman wrote:
I already fixed this issue, but I fixed it as part of #3902, which still needs to get fixed. So I decided to make this it owns separate ticket since it is a pretty serious issue.
Yeah I remember. It is indeed pretty serious. Can you submit a patch that addresses just this bug, since it doesn't look like we have a clear solution for #3902 yet?