[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 nothi

[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/

[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

[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

[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 Th

[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 -

[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 subsc