I guess I wonder why "unfortunate timing" should cause this to behave in such a way? Is this a bug? Shouldn't the cluster behavior be consistent if a node is truly leaving gracefully?
On Aug 26, 2013, at 8:57 AM, Teemu Ollakka <email address hidden> wrote:
> It looks like inconsistent nodes tried to leave gracefully, but due to
> unfortunate timing the remaining node failed to maintain PC. As a
> workaround set wsrep_provider_options='pc.bootstrap=1' to restore PC.
I guess I wonder why "unfortunate timing" should cause this to behave in such a way? Is this a bug? Shouldn't the cluster behavior be consistent if a node is truly leaving gracefully?
On Aug 26, 2013, at 8:57 AM, Teemu Ollakka <email address hidden> wrote:
> It looks like inconsistent nodes tried to leave gracefully, but due to options= 'pc.bootstrap= 1' to restore PC.
> unfortunate timing the remaining node failed to maintain PC. As a
> workaround set wsrep_provider_
Jay Janssen, MySQL Consulting Lead, Percona about.me/ jay.janssen
http://