-
Notifications
You must be signed in to change notification settings - Fork 509
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
MongoDB replicaset with PS or PSS setup could not have arbiter added due to crashloop for goal state #1615
Comments
@KarooolisZi thanks for opening the issue! We will try to have a look at it. |
@KarooolisZi can you also please supply the agenthealth status file and agent logs (you can see more in the github issue template on how to retrieve them) |
Hi @nammn updated issue with required information |
@nammn any updates? |
Due to mentioned reason my 3 member set crashed. I can't revive them because first node is created as secondary (they had similar priority) and yet I can't initiate elections as primary is not recreated |
@nammn any updates? |
This issue is being marked stale because it has been open for 60 days with no activity. Please comment if this issue is still affecting you. If there is no change, this issue will be closed in 30 days. |
@nammn Hello, is there any progress? |
Hey i'm facing the same issue, is there any news ? |
@KarooolisZi Hey, i just found a way to make it work, a painfull one but it does work. Maybe it's only the config file of each replicaset that u need to delete ? I just deleted all PVC and it worked. |
@nammn Hello, I am not able to add arbiter to 2 member replicaset. (Same for 3 member replicaset). After adding, the pod is created however operator throws error about not reaching the goal state. After some time replicaset members go down as readiness probe is failed.
What did you do to encounter the bug?
Steps to reproduce the behavior:
What did you expect?
Arbiter to be added to 2 member replicaset. Both 2 members and 1 arbiter to reach goal state.
What happened instead?
Neither members or arbiter could reach goal state. Replicaset stuck in crashloop. Working members become failed after not reaching goal state for some time, too.
Operator Information
Kubernetes Cluster Information
If possible, please include:
mongo-<>
. For instance:kubectl get mdbc -oyaml
kubectl get sts -oyaml
kubectl exec -it mongo-0 -c mongodb-agent -- cat /var/lib/automation/config/cluster-config.json
kubectl exec -it mongo-0 -c mongodb-agent -- cat /var/log/mongodb-mms-automation/healthstatus/agent-health-status.json
kubectl exec -it mongo-0 -c mongodb-agent -- cat /var/log/mongodb-mms-automation/automation-agent-verbose.log
kubectl exec -it mongo-0 -c mongodb-agent -- cat /var/log/mongodb-mms-automation/automation-agent.log
The text was updated successfully, but these errors were encountered: