<div dir="ltr"><div><div><div><div><div><div><div>Hi all,<br><br></div>I'm not sure if you all have heard
about Raft Consensus Algorithm, but from the paper, video, and slides on
the Internet, I think that this algorithm can help to solve a lot of
distributed cases in GlusterFS.<br><br></div>For example, right now the
initial mounting of the filesystem can use any nodes IP, and later when
the application needs to read or write the data, it will randomly picked
from the peer list<br><br></div>With Raft, one of the node will act as a
master, after successful election among the peers. With one master in
place, the read/write can directly goes to the master, which will
replicate to other follower, according to the distribution requirement
(distribute, replicate, stripe, distribute-replicate, etc)<br><br></div>I also believe that with this method (having a master), the lock issue happen with samba could be reduced or resolved.<br><br></div>For more information, please visit<br>
<a href="http://raftconsensus.github.io/">http://raftconsensus.github.io/</a><br><a href="https://www.youtube.com/watch?v=YbZ3zDzDnrw">https://www.youtube.com/watch?v=YbZ3zDzDnrw</a><br><br></div>and the paper<br><a href="http://ramcloud.stanford.edu/raft.pdf">http://ramcloud.stanford.edu/raft.pdf</a><br>
<br></div>Thanks. <br><div><div><div><div><div><div><div><div></div><br clear="all"><br>-- <br>Sharuzzaman Ahmat Raslan
</div></div></div></div></div></div></div></div>