[Bug 1583521] [NEW] After a network split, a node can make a write progress and end-up with a diverged local seqno
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
[Bug 1583521] Re: After a network split, a node can make a write progress and end-up with a diverged local seqno
** Description changed: How to reproduce: Given: - * A cluster of 5 Galera nodes (percona packages) + * 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. + * auto-recovery decisions made by 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. -- 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
[Bug 1583521] Re: After a network split, a node can make a write progress and end-up with a diverged local seqno
https://github.com/codership/galera/issues/401 -- 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
[Bug 1583521] Re: After a network split, a node can make a write progress and end-up with a diverged local seqno
** Changed in: codership-mysql Status: New => Invalid -- 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
[Bug 1437359] [NEW] A PIDFILE is double-defined for the corosync-notifyd init script
Public bug reported: A /etc/init.d/corosync-notifyd contains two definitions for the PIDFILE: > PIDFILE=/var/run/$NAME.pid > SCRIPTNAME=/etc/init.d/$NAME > PIDFILE=/var/run/corosync.pid The first one is correct and the second one is wrong as it refers to the corosync service's pidfile instead The corosync package version is 2.3.3-1ubuntu1 ** Affects: corosync (Ubuntu) Importance: Undecided Status: New ** Tags: trusty ** Description changed: A /etc/init.d/corosync-notifyd contains two definitions for the PIDFILE: > PIDFILE=/var/run/$NAME.pid > SCRIPTNAME=/etc/init.d/$NAME > PIDFILE=/var/run/corosync.pid The first one is correct and the second one is wrong as it refers to the corosync service's pidfile instead + + The corosync package version is 2.3.3-1ubuntu1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1437359 Title: A PIDFILE is double-defined for the corosync-notifyd init script To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1437359/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1437368] [NEW] A DAEMON_ARGS="-d" is missing for the corosync-notifyd init script
Public bug reported: Without a -d option, corosync-notifyd refuses to start with the command start-stop-daemon --verbose --start --exec /usr/sbin/corosync-notifyd -- But it starts OK with start-stop-daemon --verbose --start --exec /usr/sbin/corosync-notifyd -- -d According to the man pages, the -d option should be used in order to make the corosync-notifyd to send DBUS signals on all events, so it looks like is *should* present as well The corosync package version is 2.3.3-1ubuntu1 ** Affects: corosync (Ubuntu) Importance: Undecided Status: New ** Tags: trusty ** Tags added: trusty ** Description changed: Without a -d option, corosync-notifyd refuses to start with the command start-stop-daemon --verbose --start --exec /usr/sbin/corosync-notifyd -- But it starts OK with start-stop-daemon --verbose --start --exec /usr/sbin/corosync-notifyd -- -d According to the man pages, the -d option should be used in order to make the corosync-notifyd to send DBUS signals on all events, so it looks like is *should* present as well + + The corosync package version is 2.3.3-1ubuntu1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1437368 Title: A DAEMON_ARGS="-d" is missing for the corosync-notifyd init script To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1437368/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1445616] Re: crmsh in vivid/wily/xenial is not compatible with pacemaker
AFAICT, for the current xenial, the pacemaker is 1.1.14 and crmsh v2.1.4 is "old" again. Works for me with https://launchpad.net/ubuntu/+source/crmsh/2.2.0-1/+build/8964914/+files/crmsh_2.2.0-1_amd64.deb -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1445616 Title: crmsh in vivid/wily/xenial is not compatible with pacemaker To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crmsh/+bug/1445616/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
