13 thoughts on “Run multiple garbd arbitrator instances for galera”
how good that I do not have to understand 😂
Everything is fine 🤓
Doesn’t it need at least 3 nodes? (Or precisely 2 nodes an 1 arbitrator)?
Did you loop it then over TCP or could garbd handle it through the PID?
Ha! Got it! That’s good to know!
It does. It’s 2 clusters but 1 off site monitoring server providing now 2 arbitrators for quorum to handle splitbrain situations of each cluster better. And they are even running different galera versions 🤯 It just works. Really not missing pacemaker/corosync|heartbeat + drbd.
Que? xD
3 Tasks und garbd macht Child-Prozesse auf. War der Meinung, das geht nicht auf dem gleichen Blech, hab’s aber auch noch nie ausprobiert.
Danke für den „Vorturner“ (oder Hinweis)!
That’s an artifact of the spawn process. Systemd starts the daemon and this one forks. In the end it’s running as nobody (or user – handy for ssl certs)
garbd runs TCP communications but it’s SysVinit script can not deal with multiple instances of the daemon on the same VM ootb.
Yo. That kind a parametrized start up for the two boxes. Got it.
Yeah. Bonus for keeping an eye on cpu/mem usage, auto restart on failure, secure logging and keeping it running without more scripts to check on the process. That’s all ootb with systemd.
The only monitoring left to do is the cluster/machine health. I roll with Zabbix on this 😇
This sounds not experimental anymore… that’s a productive system… ☺️☺️☺️
Far above my needs…
But hey, I’m already writing down not to lose it… 🙏🏻🙏🏻🙏🏻
oc it’s productive 😆
Let me know if you need help – via TG or something 🙃
how good that I do not have to understand 😂
Everything is fine 🤓
Doesn’t it need at least 3 nodes? (Or precisely 2 nodes an 1 arbitrator)?
Did you loop it then over TCP or could garbd handle it through the PID?
Ha! Got it! That’s good to know!
It does. It’s 2 clusters but 1 off site monitoring server providing now 2 arbitrators for quorum to handle splitbrain situations of each cluster better. And they are even running different galera versions 🤯 It just works. Really not missing pacemaker/corosync|heartbeat + drbd.
Que? xD
3 Tasks und garbd macht Child-Prozesse auf. War der Meinung, das geht nicht auf dem gleichen Blech, hab’s aber auch noch nie ausprobiert.
Danke für den „Vorturner“ (oder Hinweis)!
That’s an artifact of the spawn process. Systemd starts the daemon and this one forks. In the end it’s running as nobody (or user – handy for ssl certs)
garbd runs TCP communications but it’s SysVinit script can not deal with multiple instances of the daemon on the same VM ootb.
Yo. That kind a parametrized start up for the two boxes. Got it.
Yeah. Bonus for keeping an eye on cpu/mem usage, auto restart on failure, secure logging and keeping it running without more scripts to check on the process. That’s all ootb with systemd.
The only monitoring left to do is the cluster/machine health. I roll with Zabbix on this 😇
This sounds not experimental anymore… that’s a productive system… ☺️☺️☺️
Far above my needs…
But hey, I’m already writing down not to lose it… 🙏🏻🙏🏻🙏🏻
oc it’s productive 😆
Let me know if you need help – via TG or something 🙃