documentation incorrectly states wsrep_recover will assign the recovered position for server start

[Jay Janssen]

http://www.percona.com/doc/percona-xtradb-cluster/wsrep-index.html#wsrep_recover

States:

When server is started with this variable it will parse Global Transaction ID from log, and if the GTID is found, assign it as initial position for actual server start. This option is used to recover GTID.

AFAICT, the GTID is only outputted, it is not assigned to the grastate.dat. That must be done either by editing the grastate.dat or by using --wsrep_start_position

[Raghavendra D Prabhu (raghavendra-prabhu)]

The old link seems to be gone.

The new link is:
http://www.percona.com/doc/percona-xtradb-cluster/wsrep-system-index.html

Yes, it outputs only the GTID.

[Jay Janssen (jay-janssen)]

Ok, I take this bug back (at least how I originally thought of it). Given a node that I kill -9'ed. On restart, the recover step is correctly setting the start position automatically:

130302 06:48:55 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
130302 06:48:55 mysqld_safe WSREP: Running position recovery with --log_error=/tmp/tmp.mwI4iVaIvz
130302 06:49:01 mysqld_safe WSREP: Recovered position 8797f811-7f73-11e2-0800-8b513b3819c1:314673
130302 6:49:01 [Note] WSREP: wsrep_start_position var submitted: '8797f811-7f73-11e2-0800-8b513b3819c1:314673'

130302 6:49:01 [Note] WSREP: Found saved state: 8797f811-7f73-11e2-0800-8b513b3819c1:-1

130302 6:49:01 [Note] WSREP: Start replication130302 6:49:01 [Note] WSREP: Setting initial position to 8797f811-7f73-11e2-0800-8b513b3819c1:314673

[Raghavendra D Prabhu (raghavendra-prabhu)]

Updated appropriately.

[Shahriyar Rzayev (rzayev-sehriyar)]

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-1052