[MDEV-17623] Cannot Initialize a New Cluster using /usr/bin/galera_new_cluster Created: 2018-11-06  Updated: 2018-11-20  Resolved: 2018-11-20

Status: Closed
Project: MariaDB Server
Component/s: Documentation, Galera
Affects Version/s: 10.3.10
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Test Jetco Assignee: Ian Gilfillan
Resolution: Fixed Votes: 0
Labels: galera
Environment:

RedHat Enterprise 7.3

Attachments: Text File mariadb installation log.txt    

 Description   

I have installed mariadb 10.3.10 rpm version. I established 3 nodes. On the first node, I execute the following command to initialize the cluster:

# cd /usr/bin
 
# ./galera_new_cluster

It was done successfully. However, when I queried the result, it showed the following:

> mysql -u root
 
Welcome to the MariaDB monitor.  Commands end with ; or \g.
 
Your MariaDB connection id is 8
 
Server version: 10.3.10-MariaDB MariaDB Server
 
 
 
Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.
 
 
 
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
 
 
 
MariaDB [(none)]> SHOW STATUS LIKE 'wsrep_%';
 
+--------------------------+----------------------+
 
| Variable_name            | Value                |
 
+--------------------------+----------------------+
 
| wsrep_cluster_conf_id    | 18446744073709551615 |
 
| wsrep_cluster_size       | 0                    |
 
| wsrep_cluster_state_uuid |                      |
 
| wsrep_cluster_status     | Disconnected         |
 
| wsrep_connected          | OFF                  |
 
| wsrep_local_bf_aborts    | 0                    |
 
| wsrep_local_index        | 18446744073709551615 |
 
| wsrep_provider_name      |                      |
 
| wsrep_provider_vendor    |                      |
 
| wsrep_provider_version   |                      |
 
| wsrep_ready              | OFF                  |
 
| wsrep_thread_count       | 0                    |
 
+--------------------------+----------------------+
 
12 rows in set (0.001 sec)

wsrep_cluster_size is 0, not 1. Why?

 Comments   
Comment by Elena Stepanova [ 2018-11-06 ]

I would think it's because you don't have wsrep_on. But our current documentation seems to contradict it, saying that the value of the variable doesn't affect the membership. Assigning to jplindst to clarify.

Comment by Teemu Ollakka [ 2018-11-09 ]

The documentation is not clear between the difference between GLOBAL and SESSION variable. If GLOBAL wsrep_on=OFF, it should not be possible to load provider and join the node in the cluster. However, if SESSION wsrep_on is set to OFF, the operations from that particular session are not replicated in the cluster, but other sessions and applier threads will continue as normal.

Comment by Elena Stepanova [ 2018-11-09 ]

teemu.ollakka,
So, it actually works as expected, and we should move it to documentation?

Comment by Jan Lindström (Inactive) [ 2018-11-12 ]

Galera cluster will be created and used if and only if wsrep_on=ON and wsrep provider library can be loaded.

Comment by Jan Lindström (Inactive) [ 2018-11-12 ]

greenman Can you clarify the documentation in above ^

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