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

..

joint_autoleave.txt

raft: initialize new Progress at LastIndex, not LastIndex+1

2019-08-14 20:53:34 +02:00

joint_idempotency.txt

raft: initialize new Progress at LastIndex, not LastIndex+1

2019-08-14 20:53:34 +02:00

joint_learners_next.txt

raft: initialize new Progress at LastIndex, not LastIndex+1

2019-08-14 20:53:34 +02:00

joint_safety.txt

raft: initialize new Progress at LastIndex, not LastIndex+1

2019-08-14 20:53:34 +02:00

simple_idempotency.txt

raft: initialize new Progress at LastIndex, not LastIndex+1

2019-08-14 20:53:34 +02:00

simple_promote_demote.txt

raft: initialize new Progress at LastIndex, not LastIndex+1

2019-08-14 20:53:34 +02:00

simple_safety.txt

raft: initialize new Progress at LastIndex, not LastIndex+1

2019-08-14 20:53:34 +02:00

update.txt

raft: initialize new Progress at LastIndex, not LastIndex+1

2019-08-14 20:53:34 +02:00

zero.txt

raft: initialize new Progress at LastIndex, not LastIndex+1

2019-08-14 20:53:34 +02:00