lp:~percona-core/percona-xtradb-cluster/pxc-5.5.41-pkging
Created by
Raghavendra D Prabhu
and last modified
- Get this branch:
- bzr branch lp:~percona-core/percona-xtradb-cluster/pxc-5.5.41-pkging
Members of
Percona core
can upload to this branch. Log in for directions.
Branch merges
Propose for merging
No branches
dependent on this one.
- Alexey Kopytov (community): Approve
-
Diff: 2003 lines (+907/-418)31 files modifiedMakefile-pxc (+2/-2)
build-ps/debian/changelog.ps (+8/-0)
build-ps/debian/rules (+1/-0)
build-ps/percona-xtradb-cluster.spec (+47/-40)
build-ps/rpm/mysql-systemd (+19/-3)
mysql-test/r/grant.result (+13/-0)
mysql-test/r/grant_cache_no_prot.result (+2/-0)
mysql-test/r/openssl_1.result (+2/-2)
mysql-test/r/percona_bug1354988.result (+50/-0)
mysql-test/r/percona_log_slow_sp_statements.result (+3/-3)
mysql-test/std_data/cacert.pem (+77/-15)
mysql-test/std_data/client-cert.pem (+73/-37)
mysql-test/std_data/client-key.pem (+25/-13)
mysql-test/std_data/server-cert.pem (+73/-32)
mysql-test/std_data/server-key.pem (+25/-7)
mysql-test/std_data/server8k-cert.pem (+205/-49)
mysql-test/std_data/server8k-key.pem (+97/-97)
mysql-test/t/openssl_1.test (+2/-2)
mysql-test/t/percona_bug1354988.test (+53/-0)
mysql-test/t/percona_log_slow_sp_statements.test (+3/-3)
percona-xtradb-cluster-tests/conf/conf20.cnf-node1 (+1/-1)
percona-xtradb-cluster-tests/conf/conf20.cnf-node2 (+1/-1)
percona-xtradb-cluster-tests/run.sh (+4/-1)
scripts/clustercheck.sh (+0/-92)
scripts/mysqld_safe.sh (+16/-2)
scripts/wsrep_sst_xtrabackup-v2.sh (+84/-6)
sql/log.cc (+1/-1)
sql/sql_acl.cc (+7/-3)
storage/innobase/include/univ.i (+1/-1)
storage/innobase/lock/lock0lock.c (+1/-1)
storage/innobase/srv/srv0start.c (+11/-4)
Related source package recipes
Branch information
- Owner:
- Percona core
- Status:
- Development
Recent revisions
- 849. By Raghavendra D Prabhu
-
Bug#1396757 rhel7 / systemd -- killing mysqld causes lingering systemd processes
- 847. By Raghavendra D Prabhu
-
Bug#1378578 Resume mysqld startup in case wsrep-recover fails
With an unclean SST, it is possible that data directory is not in a sane
state and wsrep-recover can fail in non-deterministic ways. In this
case, it makes sense to go ahead with mysqld startup to start a new SST
or act accordingly based on grastate.dat.So, the behavior has been changed to resume when wsrep-recovery fails to
recovery anything.At the same time, an option to mysqld_safe --exit-
on-recover- fail has
been added to keep the older behavior. The default being, it doesn't
exit when recover fails.
Branch metadata
- Branch format:
- Branch format 7
- Repository format:
- Bazaar repository format 2a (needs bzr 1.16 or later)
- Stacked on:
- lp:percona-xtradb-cluster
