Also, can I reduce the time for the backup server to be active from 2 minutes to 1 minute or 45 seconds when primary is not available? I'm using Artemis version 2.19.1.
From: Gunawan, Rahman (GSFC-703.H)[Halvik Corp] Sent: Wednesday, April 6, 2022 11:06 AM To: [email protected] Subject: Configuration check-for-live-server recommendation for backup server Hi, I would like to recommend to add configuration "<check-for-live-server>" to backup server. I tested artemis replication mode with the following configuration: Primary: <ha-policy> <replication> <master> <vote-on-replication-failure>true</vote-on-replication-failure> <check-for-live-server>true</check-for-live-server> </master> </replication> </ha-policy> Backup server: <ha-policy> <replication> <slave> <allow-failback>false</allow-failback> </slave> </replication> </ha-policy> We also enable ping on both primary and backup server. 1. When the network card in primary was disabled, after around 2 minutes, the backup server went live while the primary server was still isolated from network. 2. After network card in primary server was enabled, artemis in primary woke up but it detected a live server was already active so it announced as backup. 3. Then, network card in the backup server was disabled, after around 2 minutes, the primary server went live while the backup server was still isolated from network. 4. After network card in the backup server was enabled, the backup server woke but because there was no configuration to check for live server, it went live while the primary server also live (split brain issue). Any reason why the backup server doesn't have configuration "<check-for-live-server>"? Thanks Regards, Rahman
