upstream is closed will close this issue too.
** Changed in: percona-xtradb-cluster
Status: New => Invalid
** Changed in: percona-xtradb-cluster-5.6 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
https://groups.google.com/forum/#!topic/codership-team/MOuSg_tiIOI
--
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
Original bug was fixed. This bug was meant to track it so will close
this bug on PXC front.
** Changed in: percona-xtradb-cluster/5.6
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
As confirmed this is a bug in xtrabackup. Check here:
https://bugs.launchpad.net/percona-xtrabackup/+bug/1512616 and fix for
it is committed here https://github.com/gl-sergei/percona-
xtrabackup/commit/b7429736278e92f4e6d1bc370ca2d968b4811ae0. It should be
part of next xtrabackup release.
--
You
Case-1:
5.6.26 (latest one from trunk)
2.2.12 (Xtrabackup)
What I observed
* on node#2 with datadir and innodb_data_home_dir all files except ibdata1 is
created in datadir and ibdata1 is created in innodb_data_home_dir. Server
starts perfectly fine. No issue on that front.
