Code Monkey home page Code Monkey logo

mit-6.824-2016's People

Contributors

daniel-ziegler avatar jonhoo avatar stebalien avatar xiaoliwang avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

mit-6.824-2016's Issues

Raft实现中有个问题交流一下!

假如ABC三个节点,A是leader!
突然间网络断了,AB可以通信,C自己单独出来了!
于是:
AB正常服务,C自己成为了“候选人”!
按照代码逻辑,C只能拿到自己的票,所以身份一直是候选人loop!C的term一直不停的增加!
然后若干时间,网络恢复了!恰好那时候C又发起了RequestVote。而这时候C的term都比AB大,
AB自动成为FOLLOWER!(这个应该是错误的!)

我上面描述的场景代码中有解决么?还是我看漏了?

A minor change may improve the reduceF

Hi,
in line 59 of common_reduce.go, you can change it to
if err != nil && err == io.EOF from
if err != nil {
err == io.EOF can specify the error from decoder, which is EOF or other kind of errors.

Some question about warning from test_test.go

Hello, I'm doing the lab3 these days, while I find some warnings like Warning: client 0 managed to perform only 9 put operations in 1 sec?.
I think it may be some wrong decisions in my server code. So do you encounter the same situation like this and how you solve it?
Thanks in advance.

Is this line here redundant?

Line 481 in raft.go

func (rf *Raft) InstallSnapshot(args InstallSnapshotArgs,reply *InstallSnapshotReply) {
    ...
    rf.currentTerm = rf.currentTerm

I am wondering if you leave this to emphasize that we shan't keep our rf.currentTerm up-to-date with args.Term, cause Figure 13 does not mention that? Does it lead to some errors once happend?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.