[MDEV-25181] Improvement suggestion: 60-galera.cnf comes without wsrep_provider Created: 2021-03-17  Updated: 2023-04-11

Status: Open
Project: MariaDB Server
Component/s: Configuration, Galera
Affects Version/s: 10.5.9
Fix Version/s: 10.5

Type: Bug Priority: Minor
Reporter: Oli Sennhauser Assignee: Julius Goryavsky
Resolution: Unresolved Votes: 1
Labels: None
Environment:

Debian 10, CentOS 8 and Ubuntu 20.04


 Description   

When a Galera Cluster is installed a Galera config (60-galera.cnf) is provided:

[galera]

  1. Mandatory settings
    #wsrep_on = ON
    #wsrep_cluster_name = "MariaDB Galera Cluster"
    #wsrep_cluster_address = gcomm://
    #binlog_format = row
    #default_storage_engine = InnoDB
    #innodb_autoinc_lock_mode = 2
  1. Allow server to accept connections on all interfaces.
    #bind-address = 0.0.0.0
  1. Optional settings
    #wsrep_slave_threads = 1
    #innodb_flush_log_at_trx_commit = 0

In this config some outcommented variables are set. But wsrep_provider is missing!!! Without this variable the node will not start with the Galera plug-in enabled. It took me a few minutes to find out, what was missing. I guess that some newbies will take much longer and give up frustrated?

Suggestion: Add # wsrep_provider = /usr/lib/libgalera_smm.so to the config so we do not forget the parameter.

 Comments   
Comment by Koen De Bruyne [ 2023-01-12 ]

I agree to add the commented line, I lost several hours troubleshooting what is ultimately an easy fix.
If not, at least log the error somewhere when one of the `wsrep_` variables is set but galera could not be started.

Environment: Arch (Garuda) + several Ubuntu 22.04.01 servers

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