fter the others start. Once the others are up, then the 3rd finally unblocks
and starts.
Is this expected behavior in Pacemaker? Is there any way I can suppress this
behavior and get nodes to start irrespective of long start operations on other
nodes?
FWIW, if someone can explain to m
supporting altogether) features that
were in the previous dot release? It's almost like you *want* us annoying
users to go use something else.
Seriously, how am I supposed to edit CRM configurations on the command line
with the provided tools?
Jay Janssen, MySQL Consulting Lead, Pe
up. How can I specify
the Master role? The following colocation rule works fine:
colocation writer_vip_on_master inf: writer_vip ms_MySQL:Master
Jay Janssen, MySQL Consultant, Percona Inc.
Telephone: +1 888 401 3401 ext 563 (US/Eastern)
Emergency:
