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

NACK does not handle a restart of the NATS server(s) #202

Open
svenfoo opened this issue Sep 9, 2024 · 2 comments
Open

NACK does not handle a restart of the NATS server(s) #202

svenfoo opened this issue Sep 9, 2024 · 2 comments
Labels
defect Suspected defect such as a bug or regression

Comments

@svenfoo
Copy link

svenfoo commented Sep 9, 2024

What version were you using?

nack chart 0.26.1 (natsio/jetstream-controller:0.15.1)
nats chart 1.2.4 (nats:2.10.20-alpine)

What environment was the server running in?

Linux, k3s

Is this defect reproducible?

  • Set up the NATS server with JetStream, but select the memory backend, not file based streams.
  • Define some streams and consumers that NACK should handle.

Up until here this works fine. The NATS server starts, NACK creates the streams and consumers.

  • Now restart the NATS server.

Given the capability you are leveraging, describe your expectation?

I would expect NACK to realize that NATS was restarted and that it needs to do its job of creating the configured resources.

Given the expectation, what is the defect you are observing?

Nothing happens. The configured resources are only recreated after manually restarting NACK.

@svenfoo svenfoo added the defect Suspected defect such as a bug or regression label Sep 9, 2024
@Jarema
Copy link
Member

Jarema commented Sep 11, 2024

Hey!

We are working on NACK having proper control loop.
That will address the issue.

@svenfoo
Copy link
Author

svenfoo commented Nov 7, 2024

@Jarema Any progress on this? Can we help with this task?

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