News for hackers. Stuff that matters.
Re:ZooKeeper vs. Doozer vs. Etcd by babo on Wednesday September 11, 2013 @11:17AM (#6367706)
> raft doesn't allow reading directly from followers,

In raft all client connections to followers redirected to use the current master.

> i think they did paxos a disadvantage by not just focusing on multi-paxos

Raft is equivalent to (multi-)Paxos

Re:ZooKeeper vs. Doozer vs. Etcd by nieksand on Wednesday September 11, 2013 @09:50PM (#6371530)
Having followers redirect to the leader is how the paper describes the algorithm.

But I don't think there is anything stopping you from having followers service committed log entry reads, provided you're willing to live with being out-of-date.

Re:ZooKeeper vs. Doozer vs. Etcd by tomjohnson3 on Thursday September 12, 2013 @09:39AM (#6373887)
i don't think this is the case. here is a link to a video by one of the authors about log repair during leader election:

http://www.youtube.com/watch?feature=player_detailpage&v=YbZ...

log entries on a follower may get rolled back - and thrown out - since they were not accepted on a majority of followers.

Re:ZooKeeper vs. Doozer vs. Etcd by codexon on Wednesday September 11, 2013 @11:30PM (#6371884)
Does this mean that there is no read scaling?

The master server must be able to handle the entire read load?