This is also issue for the percona-cluster charm which can't safely remove the unit - it should shut down mysql prior removing the unit but it can't do so as there is no way to tell on which endpoint of the relation the -departed hook is running (if it's on the unit to be removed then mysql should be stopped, but not on the other one!).
Hi.
This is also issue for the percona-cluster charm which can't safely remove the unit - it should shut down mysql prior removing the unit but it can't do so as there is no way to tell on which endpoint of the relation the -departed hook is running (if it's on the unit to be removed then mysql should be stopped, but not on the other one!).
Introducing a hook that would fire before -departed, only on unit that is about to depart relation, would solve this issue. /bugs.launchpad .net/charms/ +source/ percona- cluster/ +bug/1514472)
(Here is the percona-cluster related bug: https:/