Public bug reported:

How to reproduce:

Given:
* A cluster of 5 Galera nodes (percona packages) 
* running in the multi-master writes/reads layout,
* auto-recovery decisions made my the custom Pacemaker OCF RA, it can only 
monitor/stop/start the mysqld_safe, no more interference, it removes nothing in 
the data path.

With that, do multiple runs of custom jepsen tests with Nemesis in the
random network-split partitions mode (all links and details about test
cases I described here https://goo.gl/VHyIIE , although that's tl;dr).

Results:
Expected: nodes will always recover after partitions with a merged state, 
isolated nodes can't make write progress w/o quorum.

Actual: a node (the n5 here) have done write progress, diverged, and refuses to 
start with the errors like:
[ERROR] WSREP: Local state seqno (189675) is greater than group seq no 
(188050): states diverged.

Logs, package versions, configs and wsrep status/vars are attached.

** Affects: codership-mysql
     Importance: Undecided
         Status: New

** Affects: percona-xtradb-cluster
     Importance: Undecided
         Status: New

** Affects: percona-xtradb-cluster-5.6 (Ubuntu)
     Importance: Undecided
         Status: New

** Attachment added: "mysql_logs.tgz"
   
https://bugs.launchpad.net/bugs/1583521/+attachment/4666139/+files/mysql_logs.tgz

** Also affects: percona-xtradb-cluster
   Importance: Undecided
       Status: New

** Also affects: percona-xtradb-cluster-5.6 (Ubuntu)
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1583521

Title:
  After a network split, a node can make a write progress and end-up
  with a diverged local seqno

To manage notifications about this bug go to:
https://bugs.launchpad.net/codership-mysql/+bug/1583521/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to