Details
-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
17.9.0-rc-1
-
None
-
Unknown
-
Description
In JGroupsNetworkChannel.notifyChanges the member-left notification is sent with the previous leader instead of the member that actually left, so listeners cannot know which node disappeared. In addition membersIdMap only grows: every join (each pod restart in Kubernetes) adds an entry that is never removed.
Attachments
Issue Links
- blocks
-
XWIKI-25246 Ship a Kubernetes JGroups stack (DNS_PING) and make the cluster name configurable
-
- Open
-
-
XWIKI-25253 Allow knowing which cluster member must run the tasks executed only once in the cluster
-
- Open
-
- relates to
-
XWIKI-25267 Allow knowing which cluster members left the cluster for good
-
- Open
-