efficient/epaxos issues and pull requests

#24 - Bug in scalability tests: index out of range [5]

Issue - State: open - Opened by PasinduTennage almost 2 years ago

#23 - Possible bug in try-pre-accept

Issue - State: open - Opened by devu1997 almost 2 years ago

#22 - Epaxos no batching

Pull Request - State: closed - Opened by ulgut over 3 years ago

#21 - Error in the replica message processing in mencius.go

Issue - State: open - Opened by PasinduTennage over 3 years ago

#20 - Question: How does epaxos ensure that a committed value can be recovered correctly?

Issue - State: closed - Opened by drmingdrmer over 4 years ago - 2 comments

#19 - Still trying to solve the livelock problem.

Issue - State: open - Opened by drmingdrmer over 4 years ago

#18 - epaxos-exec.go: func strongconnect never return false

Issue - State: closed - Opened by liubaohai about 5 years ago

#17 - question about the proof of Lemma 2. The recovery procedure for Thrifty Egalitarian Paxos can always make progress (as long as the system is live)

Issue - State: closed - Opened by lishulong about 5 years ago - 2 comments

#16 - why commit a instance on fast-path that requires all replicas to be reply equal in preAcceptReply

Issue - State: open - Opened by pengsven about 5 years ago - 9 comments

#15 - Why is the fast-quorum for base epaxos N-1

Issue - State: closed - Opened by pengsven about 5 years ago - 4 comments

#14 - Another solution to livelock

Issue - State: open - Opened by drmingdrmer over 5 years ago - 48 comments

#13 - Flexible

Pull Request - State: closed - Opened by otrack over 5 years ago

#12 - Why does epaxos need `seq`?

Issue - State: closed - Opened by drmingdrmer over 5 years ago - 4 comments

#11 - How to prove that `seq` of two command in a strong connected component are different?

Issue - State: closed - Opened by drmingdrmer over 5 years ago - 3 comments

#10 - epaxos.go doesn't correctly check for fast quorum on fast path

Issue - State: open - Opened by jiaochangyang about 7 years ago - 1 comment

#9 - How does the file "state.go.1k" work

Issue - State: open - Opened by maple8846 over 7 years ago

#8 - Fix port number in annotation

Pull Request - State: closed - Opened by Forec almost 8 years ago

#7 - GenPaxos not replying back to client

Issue - State: open - Opened by ibalajiarun almost 9 years ago

#6 - What are valid values for instantiating the TLA+ model?

Issue - State: open - Opened by bts about 9 years ago - 1 comment

#5 - Blocking on Communication

Issue - State: open - Opened by xiang90 about 11 years ago

#4 - refactor(epaxos.go) add comments for updateAttr and conflicts map

Pull Request - State: open - Opened by xiang90 about 11 years ago - 3 comments

#3 - all: Make go-getable.

Pull Request - State: closed - Opened by mewmew over 11 years ago - 3 comments

#2 - Correcting directory names in src/README

Pull Request - State: closed - Opened by kyunghoj over 11 years ago - 1 comment

#1 - gofmt

Pull Request - State: closed - Opened by xiang90 over 11 years ago

Ecosyste.ms: Issues

GitHub / efficient/epaxos issues and pull requests