From c4f1ad7abb454b94194424733241eaab07c33da8 Mon Sep 17 00:00:00 2001 From: Dirk Goetz Date: Thu, 9 May 2019 09:25:07 +0200 Subject: [PATCH] Docs: Add Master-Master-Replication as option for mysql --- doc/06-distributed-monitoring.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/doc/06-distributed-monitoring.md b/doc/06-distributed-monitoring.md index d5cea3a95..58730420b 100644 --- a/doc/06-distributed-monitoring.md +++ b/doc/06-distributed-monitoring.md @@ -1467,7 +1467,8 @@ features can enable [HA functionality](06-distributed-monitoring.md#distributed- Best practice is to run the database backend on a dedicated server/cluster and only expose a virtual IP address to Icinga and the IDO feature. By default, only one endpoint will actively write to the backend then. Typical setups for MySQL clusters -involve Galera, more tips can be found on our [community forums](https://community.icinga.com/). +involve Master-Master-Replication (Master-Slave-Replication in both directions) or Galera, +more tips can be found on our [community forums](https://community.icinga.com/). **Note**: All nodes in the same zone require that you enable the same features for high-availability (HA). @@ -1696,7 +1697,8 @@ endpoint from the satellite zones. Best practice is to run the database backend on a dedicated server/cluster and only expose a virtual IP address to Icinga and the IDO feature. By default, only one endpoint will actively write to the backend then. Typical setups for MySQL clusters -involve Galera, more tips can be found on our [community forums](https://community.icinga.com/). +involve Master-Master-Replication (Master-Slave-Replication in both directions) or Galera, +more tips can be found on our [community forums](https://community.icinga.com/). Overview: