-
Notifications
You must be signed in to change notification settings - Fork 61
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 gave up on creating a stream before NATS became available #193
Labels
defect
Suspected defect such as a bug or regression
Comments
+1 apiVersion: jetstream.nats.io/v1beta2
kind: Stream
# skipped...
status:
conditions:
- lastTransitionTime: '2024-08-29T03:14:17.636645001Z'
message: >-
failed to connect to nats-servers(nats://nats:4222): dial tcp:
lookup nats on 10.245.0.10:53: no such host
reason: Errored
status: 'False'
type: Ready
observedGeneration: 0 |
We plan to have a prpoer control loop that would make it an ongoing operation instaed of single one. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What version were you using?
NACK: 0.15.0
Nats-server: 2.10.9
What environment was the server running in?
RKE2: v1.26.4+rke2r1
Is this defect reproducible?
Before the NATS server is available, start Nack and let it attempt to create a stream more then ten times.
Given the capability you are leveraging, describe your expectation?
The stream should be recreated
Would it be possible for the "maximum queue retries" to be configurable?
See
nack/controllers/jetstream/controller.go
Line 57 in 38b4b81
Given the expectation, what is the defect you are observing?
The stream is not created
nack log:
"controller.go:478] failed to process stream: failed to create stream "...": no suitable peers for placement (10005)"
The text was updated successfully, but these errors were encountered: