Details
-
Bug
-
Status: Resolved
-
Resolution: Done
-
None
-
None
-
None
-
None
-
Operating System: All
Platform: All
-
7322
Description
Given EOS and cluster-singleton-service are used and shard-leader for EOS is located on one cluster node and service-owner (elected by cluster-singleton-service) is on another cluster node.
When node of service-owner is isolated then there is no notification sent from cluster-singleton-service to service-owner. Result is: service-owner remains active until cluster heal. When isolated node rejoins the cluster then the notification arrives and service is stopped. But this should have happened right after isolation step.
Attachments
Issue Links
- blocks
-
BGPCEP-601 B and C: rejoining isolated node causes exabgp unable to connect to any cluster node
- Resolved