[MXS-2743] Garbd Management Created: 2019-10-28  Updated: 2021-09-17  Resolved: 2021-09-17

Status: Closed
Project: MariaDB MaxScale
Component/s: N/A
Affects Version/s: None
Fix Version/s: N/A

Type: New Feature Priority: Major
Reporter: Todd Stoffel (Inactive) Assignee: Todd Stoffel (Inactive)
Resolution: Won't Do Votes: 2
Labels: Galera

Issue Links:
Relates
relates to MDEV-20920 Arbitration Open
Epic Link: Galera Compatibility

 Description   

Add garbd monitoring to galeramon.



 Comments   
Comment by Sylvain ARBAUDIE [ 2019-10-29 ]

As of today galera has an arbiter solution to preserve quorum in case of network issues.
Role of the garbd (aka galera arbitrator daemon) :
be part of the quorum to try and preserve it
relay proxy for galera messages

aas of today the garbd is just the wsrep plugin ( see there https://galeracluster.com/library/documentation/architecture.html)
with plugs so that it always happily certifies anything instantly.

moving it to maxscale monitor would provide maxscale with powerfull integration into galera cluster and would totally make sense.

Since maxscale usually runs into the same DCs as galera nodes, we could just make a direct port with some tweaks to provide informations to the monitor.
Yet the best integration would be : having codership separating the replication traffic from the quorum calculation traffic in some way. tahtwould mean we could have a quorum member that doesnt replicate. it could even lead to garbd like piecs of software using vrrp or consul for automatic topology management.

i will add some design schemas in the coming days.

Generated at Thu Feb 08 04:16:21 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.