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

NATS consumers not pulling messages from Jetstream. Restarting NATS server solved the problem #6017

Open
funkye opened this issue Oct 18, 2024 · 1 comment
Labels
defect Suspected defect such as a bug or regression

Comments

@funkye
Copy link

funkye commented Oct 18, 2024

Observed behavior

There are messages for consumers in the stream (confirmed by analyzing the stream file and publisher logging), but the messages do not reach the consumers. NATS CLI also shows that there are no messages for these consumers.
BeforeNatsReboot

Restarting the consumers does not change anything. Restarting the server led to the messages being sent to consumers and the NATS CLI began to show other information:
AfterNatsReboot

And after consuming the message:
AfterNatsRebootMessageProcessed

The problem occurred for 13 out of 100 consumers of one stream.
There is nothing suspicious in the server logs for this period (around 15.10.2024 20:30:00)
nats_logs.zip

Expected behavior

Messages must be sent to consumers consistently.

Server and client version

NATS server version: 2.10.20, not a cluster
.NET client version: 2.2.3

Host environment

OS: Ubuntu 22.04.1

Steps to reproduce

No stable reproduce.

@funkye funkye added the defect Suspected defect such as a bug or regression label Oct 18, 2024
@neilalexander
Copy link
Member

Can you please post the nats stream info for the stream too?

It looks like before the restart, the stream sequence moves back down, which makes me think that this might be something to do with #6014. Can you please test v2.10.22 and let me know if that improves things or if the same thing happens?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
defect Suspected defect such as a bug or regression
Projects
None yet
Development

No branches or pull requests

2 participants