Scenario
- There are four machines
- Domain controller runs on machine 1
- Host controllers run on machines 2-4. Machines are called: aza, kajtek, rex.
- On each host controller two EAP servers run. One Live and one Backup.
- Test
- Start all domain components
- Wait until all backups are fully synchronized with their lives
- Kill aza machine
- Check if aza's backup (hosted on kajtek) was activated.
- Start aza machine
- Check if aza's backup (hosted on kajtek) was deactivated.
Expectation: Aza's backup, hosted on kajtek server, will do a failback and it deactivates itself.
Reality: Aza's backup, hosted on kajtek server, doesn't perform failback. It stays active.
Customer impact: Replicated HA in domain may not work as expected. After the failure/restart of one server, the EAP servers may get into the unexpected states what can lead to unavailability of service or loss of data.
In server's logs I didn't notice any unusual log messages, any errors or warnings.
- is cloned by
-
JBEAP-12013 (7.0.z) Failback is not performed in domain with 3 replicated live-backup pairs
-
- Closed
-
- is related to
-
JBEAP-12126 Replicated HA: Live doesn't failback if its journal is removed before start
-
- Closed
-
-
ENTMQBR-2184 Replicated HA: Live doesn't failback if its journal is removed before start
-
- Closed
-