Closed jfillatre closed 2 years ago
hi @helletheone , If @cwrau doesn't respond, please open a new issue.
@cwrau is there a solutions for your problem? because i have the same problem now
Sadly not, we currently have to sometimes force bootstrapping on the last node so it works again 😕
Which chart:
mariadb-galera-6.0.6 appVersion 10.6.5 Mariadb container image:
docker.io/bitnami/mariadb-galera:10.4.22-debian-10-r20
Describe the bug
Previously with 4.3.3 chart and
10.1.46-debian-10-r17
image tag, I was able to cleanly restart a cluster by scaling down/scaling up the Statefulset. I was also able to recover a unclean cluster failure apply documented procedure, and re applying initial chart configuration after a graceful shutdown.It can't be done with 10.4.22-debian-10-r20 container image, first node never able to start:
I can also reproduce with latest 6.2.0 chart and
10.6.5-debian-10-r35
. However the10.6.4-debian-10-r30
is not affected by the issue. I've patched10.4.22-debian-10-r20
script in this way to fix the issue:To Reproduce
Steps to reproduce the behavior:
10.4.22-debian-10-r20
k scale statefulset mariadb-galera --replicas=3
k scale statefulset mariadb-galera --replicas=0
k logs mariadb-galera-0 mariadb-galera -f
Expected behavior
I must be able to cold restart a gracefully shudown cluster or re apply initial configuration to a manual repaired cluster
Additional context