-
- Downloads
RAFT: Support node restarts.
- Implement a persistent WAL based on RocksDB. We use RocksDB because given a RAFT entry at index i, all the entries which exist after i need to be deleted. So, RocksDB became a natural choice to write such a thing. - Also, each server can run multiple RAFT groups, and we want to store them all in one persistent storage. - Batch all messages to be sent to other nodes, with a small timeout of 10ms. Ignore any nodes which are down and can't receive messages, or any other errors. RAFT would automatically retry those. - Remove code from cluster and commit package.
Showing
- cluster/doc.go 0 additions, 26 deletionscluster/doc.go
- cluster/predicates.go 0 additions, 50 deletionscluster/predicates.go
- cluster/predicates_test.go 0 additions, 60 deletionscluster/predicates_test.go
- cluster/shardinfo.go 0 additions, 5 deletionscluster/shardinfo.go
- cmd/dgraph/main.go 31 additions, 26 deletionscmd/dgraph/main.go
- commit/log.go 0 additions, 513 deletionscommit/log.go
- commit/log_test.go 0 additions, 267 deletionscommit/log_test.go
- raftwal/wal.go 134 additions, 0 deletionsraftwal/wal.go
- store/store.go 11 additions, 8 deletionsstore/store.go
- worker/draft.go 165 additions, 53 deletionsworker/draft.go
- worker/groups.go 7 additions, 12 deletionsworker/groups.go
cluster/doc.go
deleted
100644 → 0
cluster/predicates.go
deleted
100644 → 0
cluster/predicates_test.go
deleted
100644 → 0
cluster/shardinfo.go
deleted
100644 → 0
commit/log.go
deleted
100644 → 0
commit/log_test.go
deleted
100644 → 0
raftwal/wal.go
0 → 100644
Please register or sign in to comment