[FIXED] AckAll on replicated Interest stream #6587
Merged
+74
−15
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.
Using a consumer with
AckAll
on an Interest-based stream would not properly remove messages below the sequence as part of theAckAll
.It would not work on the leader because in
processReplicatedAck
the skipped aheado.asflr
(=sseq
) is used, so thesagap = sseq - o.asflr
would actually besagap == 0
. But usingstate.AckFloor.Stream
also doesn't work and results insagap == 0
, becauseo.store.UpdateAcks(dseq, sseq)
is called first.Should use the state prior to updating for both cases.
Signed-off-by: Maurice van Veen [email protected]