Public bug reported:
The startup order for nodes in a MySQL cluster should be Management,
Data, SQL as you don't really want a SQL node to be able to talk to the
cluster if the cluster isn't running yet.
Currently, the init scripts are installed as S19mysql-ndb-mgm, S20mysql
and S21mysql-ndb.
I would think that the problem could be easily fixed by making this
change in debian/rules
dh_installinit -a --name=mysql-ndb-mgm -- defaults 18
dh_installinit -a --name=mysql # defaults 20
dh_installinit -a --name=mysql-ndb -- defaults 19
** Affects: mysql-dfsg-5.0 (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
nodes start in incorrect order
https://launchpad.net/bugs/68119
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs