-
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 ondiscussionNeeds further discussion to reach desicionNeeds further discussion to reach desiciont:cluster:membershipt:cluster:swim
Milestone
Description
We should consider this:
- SWIM is distributed and spreads suspicion and unreachability
- TODO: check if we spread unreachability
- we gossip Members in high-level, they include reachability
- we know if a gossip is "ahead" and thus can pick the "more recent information about unreachability
- though that means we declared unreachability WITHOUT the SWIM declaring so locally, is this weird? Should we JUST rely on SWIMs to tell eachother the unreachability?
I would like to discuss this one some more, rather than just do what "we're used to" -- as our more smart failure detector does the spreading the info, so perhaps we should NOT merge this information on the high-level?
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 ondiscussionNeeds further discussion to reach desicionNeeds further discussion to reach desiciont:cluster:membershipt:cluster:swim