Failed to start mysql (max retries reached)
Bug #1745432 reported by
Jason Hobbs
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Percona Cluster Charm |
Fix Released
|
High
|
David Ames |
Bug Description
An HA deployment of charm-percona-
http://
from /var/log/
http://
The unit later made it to Ready state, but any unit going to 'error' state at any time is fatal for us.
crashdump is attached - the error was on mysql/1.
This is with commit dc19ecb from https:/
Changed in charm-percona-cluster: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
This bug is a collision when two or more units are trying to join/restart at the same time. From the logs you can see mysq/1 (the failing unit) and mysql/2 are both connecting near 15:48:0x in [0].
We have the distributed_wait function [1] that rabbitmq-server uses. This should address this issue.
[0] https:/ /pastebin. ubuntu. com/26459496/ /github. com/juju/ charm-helpers/ blob/master/ charmhelpers/ contrib/ hahelpers/ cluster. py#L370
[1] https:/