The SingletonElection will not work correct if a node crashed in EAP6

Solution Verified - Updated

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 6.x

Issue

  • If multiple services are deployed as HASingletonService with a customized election policy it might happen that the services are started on different instances. As long as the nodes are graceful stopped the election is correct. But in case of crash, long GC or network split not all services are started.

Resolution

The EAP6 HA Singleton Election work independent on each node, each node elects the services to start.
Therefor the customized election must be deterministic to have the same distribution with the same number of nodes.
Because of an issue This content is not included.BZ1325376 this election was affected and some of the services are not started correctly.

As the ElectionPolicy has been changed in EAP7, here the cluster coordinator will decide and ensure the services are started - maybe on different cluster members -, EAP7 will not have this issue.

The issue will be fixed in a later version after 6.4.8.

SBR
Product(s)
Components
Category
Tags

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.