Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Message replays on Key shared subscription are breaking ordering #7108

Merged
merged 1 commit into from
Jun 6, 2020

Conversation

merlimat
Copy link
Contributor

@merlimat merlimat commented May 30, 2020

Note: this is based on top of #6791, #7104, #7105, #7106 and #7107. Once these are merged, I'll rebase here. For the sake of this review, check commit 3afe89b

Motivation

When doing replays, the key shared dispatcher is relying on the ConcurrentSortedLongPairSet for getting message ids in order. That set though is only doing a best-effort sorting, resulting in out of order errors. We need to ensure the ordering.

@merlimat merlimat added the type/bug The PR fixed a bug or issue reported a bug label May 30, 2020
@merlimat merlimat added this to the 2.6.0 milestone May 30, 2020
@merlimat merlimat self-assigned this May 30, 2020
@codelipenghui codelipenghui merged commit c0260e9 into apache:master Jun 6, 2020
cdbartholomew pushed a commit to kafkaesque-io/pulsar that referenced this pull request Jul 24, 2020
huangdx0726 pushed a commit to huangdx0726/pulsar that referenced this pull request Aug 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/bug The PR fixed a bug or issue reported a bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants