Ticket #194 (new enhancement)
Avoid that all leader roles are claimed by the first started Lily node
| Reported by: | bruno | Owned by: | bruno |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | Process (node setup) | Version: | |
| Keywords: | Cc: |
Description
Currently there is a good chance that one Lily node will take all leader roles (indexer master, rowlog processor, possibly others).
Besides concentrating all this work on one node, it also means that if this node fails all these tasks will fail together.
Maybe we should bring some randomness in the leader election (if this is possible). Related to this, we could also think of explicit configuration of a preferred node for certain leader roles.
Note: See
TracTickets for help on using
tickets.
Another way to think about this is that the ZK-based leader election would serve to elect one node as coordinator (master), and this coordinator would then be responsible for assigning the various tasks to the various Lily nodes. This kind of thing will be needed anyway once we have multiple rowlog shards, since then we will have many more processes to assign to nodes.