SQL_SLAVE_SKIP_COUNTER=1 sticks permanently with wsrep_mysql_replication_bundle set

Bug #1169326 reported by Jay Janssen
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MySQL patches by Codership
Fix Released
Undecided
Seppo Jaakola
Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC
Fix Released
Undecided
Raghavendra D Prabhu

Bug Description

PXC 5.5.29-2.7.2

Using one node as an async slave, need wsrep_mysql_replication_bundle to keep up with replication. However, I determined that if you need to use SQL_SLAVE_SKIP_COUNTER=1, this apparently never decrements back to 0, and so every replication event going forward gets skipped.

This is probably a bigger problem with wsrep_mysql_replication_bundle's implementation, but this is how it is manifesting to me. Ultimately we need this setting to work better.

Revision history for this message
Raghavendra D Prabhu (raghavendra-prabhu) wrote :
Changed in percona-xtradb-cluster:
milestone: none → 5.5.30-24.8
Changed in percona-xtradb-cluster:
status: New → Fix Committed
assignee: nobody → Raghavendra D Prabhu (raghavendra-prabhu)
Revision history for this message
Raghavendra D Prabhu (raghavendra-prabhu) wrote :
Changed in codership-mysql:
assignee: nobody → Seppo Jaakola (seppo-jaakola)
status: New → In Progress
milestone: none → 5.5.31-23.7.5
Revision history for this message
Seppo Jaakola (seppo-jaakola) wrote :
Changed in codership-mysql:
status: In Progress → Fix Committed
Changed in percona-xtradb-cluster:
status: Fix Committed → Fix Released
Changed in codership-mysql:
status: Fix Committed → Fix Released
Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

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

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.