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

Sometimes offset listeners would not be notified when registered with a replica #172

Closed
kjnilsson opened this issue Nov 22, 2024 · 0 comments · Fixed by #173
Closed

Sometimes offset listeners would not be notified when registered with a replica #172

kjnilsson opened this issue Nov 22, 2024 · 0 comments · Fixed by #173
Labels
bug Something isn't working

Comments

@kjnilsson
Copy link
Contributor

kjnilsson commented Nov 22, 2024

Describe the bug

if an offset listener was registered with a higher offset before all lower offset had been notified the lower offsets may not be notified even if their offset is available to read.

for example:

  1. empty stream
  2. register an offset listener for offset 0 against a replica
  3. register an offset listener for offset 1
  4. write a single entry and wait for applied notification
  5. no osiris_offset message is received even though offset 0 is now committed.

In terms of RabbitMQ impact this means sometimes some consumer of a stream replica may experience a delay receiving messages.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant