-
Notifications
You must be signed in to change notification settings - Fork 39
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
Manual recovery after "gcs connection failed" with one statefulset pod gone #31
Comments
We've since had a similar failure (have a look at the logs from
Full logs: kubernetes-mysql-cluster-issue-31-logs.zip |
solsson
added a commit
that referenced
this issue
Jun 4, 2020
Had a similar/identical issue again,
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
On preemtible nodes we had one instance of manual recovery, after #30. There was no
mariadb-1
pod, and-0
and-2
stayed crashlooping. The were past init but the mariadb containers exited after:This could be a case for switching from OrderedReady to Parrallel.
The solution was to scale down to zero and then back up to three again. Oddly the pods wouldn't go away at scale to zero, so I had to manually delete mariadb-2. Is that the expected behavior for OrderedReady?
The text was updated successfully, but these errors were encountered: