[MDEV-21479] Galera 4 unable to query cluster state if not primary component Created: 2020-01-15  Updated: 2023-06-07  Resolved: 2023-05-16

Status: Closed
Project: MariaDB Server
Component/s: Galera
Affects Version/s: 10.4
Fix Version/s: 10.4.31, 10.5.22, 10.6.15, 10.9.8, 10.10.6, 10.11.5, 11.0.3, 11.1.2

Type: Bug Priority: Minor
Reporter: Vincent Milum Jr Assignee: Julius Goryavsky
Resolution: Fixed Votes: 0
Labels: None


 Description    

select * from mysql.wsrep_cluster;
 
ERROR 1047 (08S01): WSREP has not yet prepared node for application use
 
 
 
select * from mysql.wsrep_cluster_members;
 
ERROR 1047 (08S01): WSREP has not yet prepared node for application use
 
 
 
select * from mysql.wsrep_streaming_log;
 
Empty set (0.001 sec)

For some reason, wsrep_streaming_log works (but is empty), but wsrep_cluster and wsrep_cluster_members both fail.

For sysadmin purposes, it would be nice to have this information available

 Comments   
Comment by Vincent Milum Jr [ 2020-01-17 ]

Just an FYI, the primary reason I need this.

With Galera 4, wsrep_incoming_addresses shows "AUTO" now, and the only way to see (that I'm aware of) which nodes are connected is via these tables. When a network split occurs, I use the information about which nodes can still communicate with which other nodes to determiner course of action. It two nodes are broken off from the main cluster at the same time, I use the information of if they can still communicate with one-another while non-primary to determine which route should be taken to resolve the issue.

Comment by Jan Lindström [ 2023-04-25 ]

https://github.com/MariaDB/server/pull/2613

Comment by Julius Goryavsky [ 2023-05-16 ]

Fix merged with head revision: https://github.com/MariaDB/server/commit/956d6c4af9e353299cce6d2ccbd7c400a1d00d70

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