Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Garbd unsafe for backups

Description

Using Galera Arbitrator for backups is unsafe, as when GARB joins the cluster it is considered as a member:

mysql> SELECT * FROM performance_schema.pxc_cluster_view; +--------------------+--------------------------------------+--------+-------------+---------+ | HOST_NAME | UUID | STATUS | LOCAL_INDEX | SEGMENT | +--------------------+--------------------------------------+--------+-------------+---------+ | garb | 5b68fcb9-ec3c-11ea-ab82-1318f8ff7045 | JOINER | 0 | 0 | | pxc-cluster-node-1 | c723cc29-ec36-11ea-b13f-e7d83faa1ea8 | DONOR | 1 | 0 | +--------------------+--------------------------------------+--------+-------------+---------+

If it dies for any reason, it affects quorum calculation. For certain situations (for instance, 1 node cluster), it makes the whole cluster unavailable, as it goes into a non-primary state. For larger clusters, it breaks failover.

Environment

None

Smart Checklist

Activity

Slava Sarzhan February 3, 2021 at 11:50 AM

Hi,

We started to use 'pc.weight=0' for garbd backup process as it was suggested by . In this case
'garbd' will be allowed to take a backup without participation in the quorum calculations.

Done

Details

Assignee

Reporter

Labels

Time tracking

3h 30m logged

Fix versions

Priority

Smart Checklist

Created September 1, 2020 at 10:29 AM
Updated March 5, 2024 at 6:08 PM
Resolved February 3, 2021 at 11:50 AM

Flag notifications