You are here

Home » Blogs » Shinguz's blog

Galera Arbitrator (garbd)

Sat, 2013-08-17 16:59 — Shinguz

It took me quite a while to find out how the beast Galera Arbitrator (garbd) works. To safe your time here a short summary:

How to start Galera Arbitrator (garbd)

shell> ./garbd --address gcomm://192.168.13.1,192.168.13.2 --group "Our Galera Cluster" --log /tmp/garbd.log --daemon

How to stop Galera Arbitrator (gardb)

shell> killall garbd

How to start Galera Arbitrator (garbd) with a configuration file

shell>./garbd --cfg /tmp/garb.cnf --daemon

The configuration file looks as follows:

#
# /etc/mysql/garb.cnf
#
address = gcomm://127.0.0.1:5671,127.0.0.1:5672,127.0.0.1:5673
group = Our Galera Cluster
options = gmcast.listen_addr=tcp://127.0.0.1:5674
log = /tmp/garbd.log

A service start/stop script can be found at: galera-src/garb/files/agrb.sh and galera-src/garb/files/garb.cnf

Taxonomy upgrade extras: 
galera
start
stop

Comments

I actually made a little upstart script (Ubuntu) - works well under Ubuntu 13.04 (rating) w/ percona xtradb cluster packages 5.5.31-23.7.5-438.raring

This is with a 2 node cluster, this is node #3 (the arbiter), group name "default"

/etc/init/garbd.conf:

# garbd - galera arbitrator

description "Galera arbitrator"

start on runlevel [2345]
stop on runlevel [!2345]

exec /usr/bin/garbd -a gcomm://db1,db2 -g default

mike503comment Tue, 2013-08-20 00:23

With Galera version 25.3.10, the "garbd" daemon would not start unless I appended the port number (default: 4567) to the IP addresses of the cluster nodes.
The failure symptom was that an exception "gu::NotSet" was thrown, without any helpful information what it was really missing.
joergcomment Wed, 2015-08-05 16:42