fragment: slightly relax offset skip behavior #437
Merged
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.
Currently we will immediately skip forward a read if it begins at offset zero.
However, we also see cases where a long-disabled task will come back online, observe an ACK, and then attempt a replay-read from an offset fixed in its recovery log. These reads block for the full offset jump threshold.
Resolve this by skipping forward any read having an offset behind the minimum available offset of journal content.
This change is