Files
etcd/raft/confchange/testdata/simple_safety.txt
Tobias Schottdorf fdaed88f14 raft: initialize new Progress at LastIndex, not LastIndex+1
Initializing at LastIndex+1 meant that new peers would not be probed
immediately when they appeared in the leader's config, which delays
their getting caught up.
2019-08-14 20:53:34 +02:00

65 lines
869 B
Plaintext

simple
l1
----
removed all voters
simple
v1
----
voters=(1)
1: StateProbe match=0 next=1
simple
v2 l3
----
voters=(1 2) learners=(3)
1: StateProbe match=0 next=1
2: StateProbe match=0 next=2
3: StateProbe match=0 next=2 learner
simple
r1 v5
----
more than one voter changed without entering joint config
simple
r1 r2
----
removed all voters
simple
v3 v4
----
more than one voter changed without entering joint config
simple
l1 v5
----
more than one voter changed without entering joint config
simple
l1 l2
----
removed all voters
simple
l2 l3 l4 l5
----
voters=(1) learners=(2 3 4 5)
1: StateProbe match=0 next=1
2: StateProbe match=0 next=2 learner
3: StateProbe match=0 next=2 learner
4: StateProbe match=0 next=8 learner
5: StateProbe match=0 next=8 learner
simple
r1
----
removed all voters
simple
r2 r3 r4 r5
----
voters=(1)
1: StateProbe match=0 next=1