You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current cluster membership eviction algorithm requires on clocks to be synced between members so that members are evicted after the proper time without updating themselves. If clocks are not synced - this could result in members being evicted too quickly or not evicted when they should be after failing.
We can consider a different membership algorithm where, instead of maintaining last updated time on each member in the shared state, we maintain a number of pings count which is incremented every time a member updates themself. If a member hasn't updated themself enough times since the last check, they are evicted.
The text was updated successfully, but these errors were encountered:
The current cluster membership eviction algorithm requires on clocks to be synced between members so that members are evicted after the proper time without updating themselves. If clocks are not synced - this could result in members being evicted too quickly or not evicted when they should be after failing.
We can consider a different membership algorithm where, instead of maintaining last updated time on each member in the shared state, we maintain a number of pings count which is incremented every time a member updates themself. If a member hasn't updated themself enough times since the last check, they are evicted.
The text was updated successfully, but these errors were encountered: