[ovs-build] Broken: openvswitch/ovs#9084 (branch-2.13 - 25a7e55)
builds at travis-ci.org
Mon Mar 9 10:41:39 UTC 2020
Build Update for openvswitch/ovs
Duration: 2 mins and 4 secs
Commit: 25a7e55 (branch-2.13)
Author: Han Zhou
Message: raft: Fix the problem of stuck in candidate role forever.
Sometimes a server can stay in candidate role forever, even if the server
already see the new leader and handles append-requests normally. However,
because of the wrong role, it appears as disconnected from cluster and
so the clients are disconnected.
This problem happens when 2 servers become candidates in the same
term, and one of them is elected as leader in that term. It can be
reproduced by the test cases added in this patch.
The root cause is that the current implementation only changes role to
follower when a bigger term is observed (in raft_receive_term__()).
According to the RAFT paper, if another candidate becomes leader with
the same term, the candidate should change to follower.
This patch fixes it by changing the role to follower when leader
is being updated in raft_update_leader().
Signed-off-by: Han Zhou <hzhou at ovn.org>
Signed-off-by: Ben Pfaff <blp at ovn.org>
View the changeset: https://github.com/openvswitch/ovs/compare/3ae90e1899c5...25a7e5547f1e
View the full build log and details: https://travis-ci.org/openvswitch/ovs/builds/659370731?utm_medium=notification&utm_source=email
You can unsubscribe from build emails from the openvswitch/ovs repository going to https://travis-ci.org/account/preferences/unsubscribe?repository=2143550&utm_medium=notification&utm_source=email.
Or unsubscribe from *all* email updating your settings at https://travis-ci.org/account/preferences/unsubscribe?utm_medium=notification&utm_source=email.
Or configure specific recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the build