-
Notifications
You must be signed in to change notification settings - Fork 5
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
Operator can't handle pods in Error state after initialisation #12
Comments
Kubernetes allows one to configure the behavior to be taken or not taken at all when a pod container(s) fail, the However, this operator explicitly disables said default behavior and instead tries and reconcile in the face of an error. Aren't logs telling you the pod is failed? |
logs for what is described above.
If you need the full log let me know so I can share it in a file. |
I think the problem may be something else...
|
When one of the pods of a AS cluster goes from Running state to Error state, AS operator is not able to recover the cluster.
Observed Behaviour
For cluster
cluster-1
with 3 nodes Running:cluster-1-2
goes to error state (because aerospike server container stoped working due different reasons)cluster-1-0
in a infinite loopcluster-1-2
How to replicate
Temporary workaround
The problem is solved by killing the pod in error state manually
The text was updated successfully, but these errors were encountered: