[MDEV-20838] Galera Cluster in ReadOnly Mode, no writing possible Created: 2019-10-16  Updated: 2020-01-12  Resolved: 2020-01-12

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

Type: Bug Priority: Major
Reporter: peter koch Assignee: Jan Lindström (Inactive)
Resolution: Incomplete Votes: 0
Labels: need_feedback
Environment:

Galera Cluster with three 10.4.7-MariaDB, Linux version 3.10 centos



 Description   

Galera Cluster with 3 nodes failed, respectively all nodes was in Read-Only state. The count of cluster members was still 3.
At the same time there were a lot of messages in Server-log like
"mysqld: 2019-10-16 3:15:20 0 [Note] WSREP: Created page /var/lib/mysql/gcache.page.000988 of size 134217728 bytes"
At the time of the problem we load about 40 GB of data (Insert Statemenst).
Our running galera config is
[galera]
binlog_format=ROW
default-storage-engine=innodb
innodb_autoinc_lock_mode=2
bind-address=0.0.0.0
wsrep_on=ON
wsrep_provider=/usr/lib64/galera-4/libgalera_smm.so
wsrep_provider_options = "gcache.size=2G;gcs.fc_factor=0.8"
wsrep_slave_threads=8
wsrep_sst_method=rsync

The problem could only be solved by

Node 3: stop
Node 2: stop
Node 1: stop

Node 1: galera_new_cluster
Node 2: rm -rf /var/lib/mysql/*
Node 2: start
Node 3: start



 Comments   
Comment by Jan Lindström (Inactive) [ 2019-12-12 ]

What you mean by nodes are read-only state? Can you provide some output and full error log ?

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