Details
-
Bug
-
Resolution: Done
-
Major
-
EAP_EWP 5.1.1
-
None
-
-
Release Notes
-
-
Documented as Resolved Issue
-
NEW
Description
When two cluster members don't see each other (network split), they will both be a master and run any HASingletons.
When they merge back together, only the new master should continue running the HASingleton.
But the HASingleton continues to run on both nodes after the merge.
This is because DistributedReplicantManagerImpl does not notify the HASingleton of the new cluster members on a merge.
This likely affects all other services that depend on DistributedReplicantManagerImpl notifications also.
Root cause is DistributedReplicantManagerImpl#addReplicant's return value is backwards.
It should "@return true, if this replicant was newly added to the map, false otherwise", but does just the opposite.