Expected Behavior
The "High availability" section in the FAQ should be explicit about what configurations work.
Current Behavior
https://github.com/Icinga/icingaweb2-module-vspheredb/blob/v1.7.1/doc/01-Installation.md
The current docs say that "using an active-active replication is the preferred way", but also says "please do not run multiple daemons writing into the same database". Does this mean that running multiple daemons is supported, but only if they write to different MariaDB instances in a cluster?
I also noticed #203, which states that the daemon should (amongst other things) "support starting multiple instances, with only one of them being active". This issue was closed as it was "implemented with v1.2". Does this mean that using multiple service instances is safe now?
Possible Solution
Update or clarify installation documentation.
Your Environment
- VMware vCenter®/ESXi™-Version: N/A
- Version/GIT-Hash of this module: v1.7.1
- Icinga Web 2 version: 2.12.1
- Operating System and version: N/A
- Webserver, PHP versions: N/A
Expected Behavior
The "High availability" section in the FAQ should be explicit about what configurations work.
Current Behavior
https://github.com/Icinga/icingaweb2-module-vspheredb/blob/v1.7.1/doc/01-Installation.md
The current docs say that "using an active-active replication is the preferred way", but also says "please do not run multiple daemons writing into the same database". Does this mean that running multiple daemons is supported, but only if they write to different MariaDB instances in a cluster?
I also noticed #203, which states that the daemon should (amongst other things) "support starting multiple instances, with only one of them being active". This issue was closed as it was "implemented with v1.2". Does this mean that using multiple service instances is safe now?
Possible Solution
Update or clarify installation documentation.
Your Environment