Cannot set wsrep_desync to OFF dynamically when set in my.cnf

Bug #1574846 reported by amit arora on 2016-04-25
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona XtraDB Cluster moved to
Fix Released
Krunal Bauskar

Bug Description

I have 3 node PXC, let's say PXC1, PXC2 and PXC3 as 3 nodes of the cluster.

PXC1 is a primary node of sorts (since it is an async slave or another mysql master).

I created PXC1 through xtrabackup from another mysql server(not PXC) and setup replication on it.
Added PXC2, which did an SST from PXC1 and was in sync later.
In PXC3, I set "wsrep_desync=ON" in my.cnf, later PXC3 did an SST from PXC2 and was in sync.

Now I tried to disable wsrep_desync on PXC3 through following command:
"set wsrep_desync = OFF", but it threw error 1231 saying value "OFF" cannot be set for this parameter.
ERROR 1231 (42000):Variable 'wsrep_desync' can't be set to the value of 'OFF'

Version 5.6.28

amit arora (amit-0923) wrote :

Version 5.6.28

description: updated
amit arora (amit-0923) wrote :

Please let me know if any other details are needed.


Krunal Bauskar (krunal-bauskar) wrote :

I have verified the issue and fix for it will be released in future. Meantime, workaround is to avoid using wsrep_desync in my.cnf.
(Anyway, it doesn't make sense to desync a node before it is synced.)

Changed in percona-xtradb-cluster:
status: New → Confirmed
assignee: nobody → Krunal Bauskar (krunal-bauskar)
Changed in percona-xtradb-cluster:
status: Confirmed → Fix Committed
Changed in percona-xtradb-cluster:
milestone: none → 5.6.29-25.15
Changed in percona-xtradb-cluster:
status: Fix Committed → Fix Released

Percona now uses JIRA for bug reports so this bug report is migrated to:

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

Other bug subscribers