-
Notifications
You must be signed in to change notification settings - Fork 348
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
[Bug]: Unstable Jaeger Deployment with Cassandra ; Cassandra STS is failing #555
Comments
Try the latest version 1.0.2 |
I upgraded to 1.0.2 and used node selector for more stable nodes (not spot instances). |
close the issue if it sorted |
I still can't seem to make Jaeger stable, I got this errors:
|
looks similar. ran into this with one of the pod keeps crashing
|
Same issue here. K8S cluster on our own machines. 3 nodes, 3 cassandra pods deployed via Jaeger's chart. Nodes were recently upgraded, and they were rebooted. Now jaeger-cassandra-2 pod is in a crashloop, complaining about lack of cassandra pod on the third node - which I assume was rebooted last. Cassandra logs mention: I have yet to figure out where exactly to add such a flag. in Jaeger's chart, adding this: storage:
cassandra:
cmdlineParams:
cassandra.consistent.rangemovement: false didn't seem to do anything. |
What happened?
Cassandra stateful set is not stable and keeps crashing.
Steps to reproduce
Expected behavior
Jaeger available with alll pods running stable.
Relevant log output
Screenshot
Additional context
Running Jaeger on a dedicated namespace on EKS.
Jaeger backend version
1.53.0
SDK
OpenTelemetry SDK.
Pipeline
No response
Stogage backend
Cassandra
Operating system
Linux
Deployment model
Kubernetes
Deployment configs
The text was updated successfully, but these errors were encountered: