lp:~akopytov/percona-xtradb-cluster/bug1384413
Created by
Alexey Kopytov
and last modified
- Get this branch:
- bzr branch lp:~akopytov/percona-xtradb-cluster/bug1384413
Only
Alexey Kopytov
can upload to this branch. If you are
Alexey Kopytov
please log in for upload directions.
Branch merges
Propose for merging
No branches
dependent on this one.
- Raghavendra D Prabhu: Pending requested
-
Diff: 24 lines (+1/-2)2 files modifiedstorage/innobase/handler/ha_innodb.cc (+0/-1)
storage/innobase/lock/lock0lock.cc (+1/-1)
Related source package recipes
Branch information
- Owner:
- Alexey Kopytov
- Status:
- Development
Recent revisions
- 910. By Alexey Kopytov
-
PXC-178: MTR merges from codership tree
Merged lp:codership-mysql/5.6 and resolved some conflicts in MTR tests.
- 907. 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
