Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

(release/v20.03) Avoid assigning duplicate RAFT IDs to new nodes #5604

Merged
merged 1 commit into from
Jun 9, 2020
Merged

(release/v20.03) Avoid assigning duplicate RAFT IDs to new nodes #5604

merged 1 commit into from
Jun 9, 2020

Commits on Jun 8, 2020

  1. Avoid assigning duplicate RAFT IDs to new nodes. (#5571) 

    Currently, zero uses the MaxRaftId to assign RAFT IDs to new nodes. However, the
MaxRaftId value is not immediately updated and the lock is released in between
creating the proposal and sending the proposal to the RAFT node. This can lead
to situations where more than one new node is assigned the same ID.

To solve this, this change introduces a new field to generate the IDs that is
updated immediately, thus preventing multiple nodes from being assigned
the same ID.

Fixes #5436
    @martinmr
    martinmr committed Jun 8, 2020
    Configuration menu
    Copy the full SHA
    df059be View commit details
    Browse the repository at this point in the history