Details
-
New Feature
-
Resolution: Fixed
-
Major
-
17.7.0
Description
The idea is to expose in the API one cluster member as a leader, and to change it automatically when the leader goes down.
It can be very useful for any feature which needs to make sure that only one of the member is doing something (for example the scheduler, which is currently manually enabled or disabled so that only one runs it).
Attachments
Issue Links
- blocks
-
XCOMMONS-3451 Realtime editing doesn't support clustering
-
- Closed
-
-
XWIKI-23474 Expose more of clustering related information in the administration UI
-
- Closed
-
-
XCOMMONS-3712 Allow making all Netflux reatime clustering events go through the leader
-
- Open
-
- is related to
-
XWIKI-25253 Allow knowing which cluster member must run the tasks executed only once in the cluster
-
- Open
-