| 2012-10-08 18:34:31 |
Daniel Nichter |
description |
Two bugs:
cluster -> PXC-based slaved
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). |
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). |
|
