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
Currently, replication events, such as updating replication progress, are
transmitted via the notify channel. Since multiple leaders(with distinct votes)
share this channel on a single node, a new leader might receive a progress event
intended for a previous leader.
This issue is resolved by comparing the vote of the leader with the progress
event. If the event's vote differs from the current leader's vote, the event
is disregarded.
To simplify this process, a separate channel can be created for each leader, and
the channel can be abandoned when a leader steps down, such as when a higher
vote is observed. This approach eliminates the need for further vote
comparisons.
The text was updated successfully, but these errors were encountered:
Currently, replication events, such as updating replication progress, are
transmitted via the
notify
channel. Since multiple leaders(with distinctvote
s)share this channel on a single node, a new leader might receive a progress event
intended for a previous leader.
This issue is resolved by comparing the
vote
of the leader with the progressevent. If the event's
vote
differs from the current leader's vote, the eventis disregarded.
To simplify this process, a separate channel can be created for each leader, and
the channel can be abandoned when a leader steps down, such as when a higher
vote is observed. This approach eliminates the need for further
vote
comparisons.
The text was updated successfully, but these errors were encountered: