Ben Darnell 32824e053c raft: Only call stableTo when we have ready entries or a snapshot. ...

The first Ready after RestartNode (with no snapshot) will have no
unstable entries, so we don't have the correct prevLastUnstablei
when Advance is called. This would cause raftLog.unstable to move
backwards and previously-stable entries would be returned to
the application again.

This should have been caught by the "unexpected Ready" portion of
TestNodeRestart, but it went unnoticed because the Node's goroutine
takes some time to read from advancec and prepare the write to read to
readyc. Added a small (1ms) delay to all such tests to ensure that the
goroutine has time to enter its select wait.

2014-11-13 14:57:01 -05:00

..

raftpb

*: support updating advertise-peer-url

2014-11-11 12:07:03 -08:00

diff_test.go

*: add license header to all source files

2014-10-17 15:41:22 -07:00

doc.go

*: add a Advance interface to raft.Node

2014-11-05 15:04:14 -08:00

example_test.go

*: add license header to all source files

2014-10-17 15:41:22 -07:00

log_test.go

raft: update unstable when calling stableTo with 0

2014-11-11 17:20:31 -08:00

log.go

raft: update unstable when calling stableTo with 0

2014-11-11 17:20:31 -08:00

node_bench_test.go

Merge pull request #1586 from xiangli-cmu/fix_node

2014-11-05 15:09:51 -08:00

node_test.go

raft: Only call stableTo when we have ready entries or a snapshot.

2014-11-13 14:57:01 -05:00

node.go

raft: Only call stableTo when we have ready entries or a snapshot.

2014-11-13 14:57:01 -05:00

raft_paper_test.go

raft: remove raftLog.resetUnstable and resetNextEnts

2014-11-06 17:18:00 -05:00

raft_test.go

raft: nodes return sorted ids

2014-11-11 22:58:15 -08:00

raft.go

raft: nodes return sorted ids

2014-11-11 22:58:15 -08:00