-
Notifications
You must be signed in to change notification settings - Fork 79
Open
Labels
1 - triagedTicket makes sense and is well defined, ready to be worked onTicket makes sense and is well defined, ready to be worked onsize/MMedium task. (A couple of days of work.)Medium task. (A couple of days of work.)t:cluster:membershipt:cluster:singleton
Milestone
Description
I don't like them to be honest... but they're easier than ad-hoc implementing a CAS thing right away.
Up numbers are assigned by the leader when doing the -> up move. They are an order of "age" the oldest member has the lowest up number. Thanks to this we know which node is the "oldest" and can get on that node being "less likely to get down" rather than some burst-y new node added during a spike.
I'd love to not have the numbers but implement a CAS / bully like singleton setting...
Metadata
Metadata
Assignees
Labels
1 - triagedTicket makes sense and is well defined, ready to be worked onTicket makes sense and is well defined, ready to be worked onsize/MMedium task. (A couple of days of work.)Medium task. (A couple of days of work.)t:cluster:membershipt:cluster:singleton