[MDEV-9231] Setting wsrep_desync in my.cnf file does not desync node Created: 2015-12-02  Updated: 2019-12-14  Resolved: 2019-12-14

Status: Closed
Project: MariaDB Server
Component/s: Galera, wsrep
Affects Version/s: 10.0.21-galera, 10.0.22-galera
Fix Version/s: N/A

Type: Bug Priority: Minor
Reporter: Jessica Kearney Assignee: Jan Lindström (Inactive)
Resolution: Won't Fix Votes: 0
Labels: Galera, desynced_node, wsrep, wsrep_desync
Environment:

Virtual Machine
CentOS 6.7 x 64bit
RAM 15GB
CPU 4 cores @ 2.7Ghz/core



 Description   

I have one of our MariaDB Galera nodes set to desync itself on startup by setting 'wsrep_desync=on' in the my.cnf file as its in a remote site and we don't need the cluster to be waiting for it to apply transactions. After starting the service and checking the sync status it always goes to Synced. When I run 'set global wsrep_desync=on;' I get a warning that it was already set to on and then when I check the sync status again it then will read 'Donor/Desynced'.

After startup while it reads "Synced" I've tried locking tables to see if it was truly synced or not and it did lock the tables for the whole cluster so I think that means it was synced. After running the command and locking them again it didn't lock them across the cluster.



 Comments   
Comment by Jan Lindström (Inactive) [ 2019-12-14 ]

Support for 10.0-galera has ended.

Generated at Thu Feb 08 07:33:07 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.