pt-table-checksum 2.1.4 miscategorizes Percona XtraDB Cluster-based slaves as cluster nodes

Reported by Brian Fraser on 2012-10-08
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Toolkit
Critical
Brian Fraser

Bug Description

Two bugs:

cluster -> PXC-based slave

The slave is tagged as a cluster node and slave lag isn't checked, even though it was wsrep_on OFF. This is because the code currently just looks for wsrep_on and doesn't check the value.

cluster1 -> cluster2

The second cluster is a slave of the first, but even if the above bug is fixed, we don't check slave lag because we assume that if wsrep_on is ON, then every cluster node will belong to the same cluster. A good 80% solution is checking that wsrep_cluster_name is the same for both nodes, but that'll still fail for clusters with the same name (i.e., the sandboxes in portable-test-suite as of now).

Brian Fraser (fraserbn) on 2012-10-08
summary: pt-table-checksum 2.1.4 miscategorizes Percona XtraDB Cluster-based
- slaves as cluster codes
+ slaves as cluster nodes
Changed in percona-toolkit:
status: New → Triaged
tags: added: percona-xtradb-cluster pt-table-checksum
Changed in percona-toolkit:
importance: Undecided → Critical
milestone: none → 2.1.5
assignee: nobody → Brian Fraser (fraserbn)
description: updated
Daniel Nichter (daniel-nichter) wrote :

Clarification on "cluster -> PXC-based slave". This happens when a node in the cluster has a traditional replication slave attached to it. That slave can be a Percona XtraDB Cluster instance but not being used as a cluster node, so wsrep_on=OFF.

Changed in percona-toolkit:
status: Triaged → Fix Committed
Changed in percona-toolkit:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers