Closed debajyoti-truefoundry closed 4 months ago
You might consider upgrading your server to the latest, which is 2.9.21 and we are about to release 2.9.22.
You might consider upgrading your server to the latest, which is 2.9.21 and we are about to release 2.9.22.
Thanks. Can I just update the nats.image.tag
field in my helm chart? Or is there an upgrade procedure? I am currently using chart version 0.19.1
.
Suggest you read release notes, at least https://github.com/nats-io/nats-server/releases/tag/v2.0.0 and also 2.1.0 ones.
We cannot tell you what will happen with such a large jump in versions, you have to test this in dev or staging.
I am closing this issue as the upgrade was smooth and solved by issue.
What version were you using?
nats-server: v2.9.8 Clients
What environment was the server running in?
Image: nats:2.9.8-alpine OS: Linux (amd64) Helm Values:
Is this defect reproducible?
Unfortunately issue is not reproducible. I have described my observations on the issue below.
I have a stream with the following info,
I create an ephemeral consumer,
And get back this response.
Even though I have a message with the subject
tfy-agent.foo.bar
on the stream I do not get back any message.Upon checking the consumer info, this is what I can see,
Upon further investigation, I observed that whenever the leader for the ephemeral consumer is
truefoundry-nats-0
pod, I do not get any message. I used the code snippet below to verify this,I get the output below in the end,
This issue was resolved after
truefoundry-nats-0
restarted.Given the capability you are leveraging, describe your expectation?
I should be getting messages regardless of the ephemeral consumer leader.
Given the expectation, what is the defect you are observing?
I do not get messages if the ephemeral consumer leader is the
truefoundry-nats-0
pod.