Ramesh Sivaraman added a comment - 2022-08-05 11:14 - edited jplindst wsrep_cluster_size becomes zero only when SST is triggered after an upgrade. Restarting the upgraded node will resolve this issue. [vagrant@node3 ~]$ sudo mysql -e"show status like '%wsrep_cluster_size%'" +--------------------+-------+ | Variable_name | Value | +--------------------+-------+ | wsrep_cluster_size | 0 | +--------------------+-------+ [vagrant@node3 ~]$ [vagrant@node3 ~]$ sudo grep -i 'SST succeeded' /var/lib/mysql/mysql-error.log 2022-08-05 11:00:14 3 [Note] WSREP: SST succeeded for position b3bf9ad6-14a7-11ed-9106-5e6aa65a6a88:4 [vagrant@node3 ~]$ [vagrant@node3 ~]$ sudo systemctl restart mariadb.service [vagrant@node3 ~]$ sudo mysql -e"show status like '%wsrep_cluster_size%'" +--------------------+-------+ | Variable_name | Value | +--------------------+-------+ | wsrep_cluster_size | 3 | +--------------------+-------+ [vagrant@node3 ~]$ If the upgraded node does't start SST, wsrep_cluster_size shows correctly after an upgrade. [vagrant@node3 ~]$ sudo mysql -e"show status like '%wsrep_cluster_size%'" +--------------------+-------+ | Variable_name | Value | +--------------------+-------+ | wsrep_cluster_size | 3 | +--------------------+-------+ [vagrant@node3 ~]$ [vagrant@node3 ~]$ sudo grep -i sst /var/lib/mysql/mysql-error.log [vagrant@node3 ~]$

Jan Lindström (Inactive) added a comment - 2022-08-25 04:59 ramesh Can you re-test with branch bb-10.4- MDEV-29246 -galera

Jan Lindström (Inactive) added a comment - 2022-08-25 09:29 As noted in error log [Warning] WSREP: View recovered from stable storage was empty. If the server is doing rolling upgrade from previous version which does not support storing view info into stable storage, this is ok. Otherwise this may be a sign of malfunction. this is not a bug. 10.3 does not store view into stable storage so to see correct wsrep_cluster_size value all nodes need to be upgraded to 10.4. Workaround as noted is to restart already upgraded 10.4 node.