ClusterLabs / ClusterLabs/resource-agents

Galera - in perpetual state of Slave

Open
#1,729 5 comments 0 reactions 0 assignees View on GitHub
Dominant language
Shell
Stars
519
Forks
608
Avg merge
6d 1h
Merged PRs (30d)
7

Description

Hi guys.
I'm on CentOS Stream 8 with pcs-0.10.12-1.el8.x86_64 trying to set up 'galera' resource.
I have:
mariadb-server-galera-10.3.28-1.module_el8.3.0+757+d382997d.x86_64
perfectly working prior but also outside - meaning then it works after pcs resource was used and stopped - but PCS 'galera' resource fails to instantiate Galera cluster.
PCS 'galera' elects a master but other nodes remain in 'Slave' state forever and on those nodes MariaDB server is not started. PCS cluster does not complain about anything specific and says that all is good seemingly being happy.

Please feel free to ask for more specific logs/info you might need.
thanks, L.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the pcs Galera resource setup on CentOS Stream 8 with the reported MariaDB and pcs versions, then collect the resource-agent and cluster logs from the master and Slave nodes. Trace why the non-master nodes remain in Slave state and why MariaDB is not started; done means the resource reports the cluster healthy only when all nodes are operating correctly.

Written by the indexing model from the issue text.

Assessment

Tech stack
mariadb, shell
Domain
databases, distributed-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.