Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

What's the consensus protocol used in the replication? #8

Closed
lshmouse opened this issue Jun 3, 2015 · 2 comments
Closed

What's the consensus protocol used in the replication? #8

lshmouse opened this issue Jun 3, 2015 · 2 comments

Comments

@lshmouse
Copy link

lshmouse commented Jun 3, 2015

Very impressive project.

I have some questions and thanks for pointing out if I am wrong.

What's the consensus protocol used in the replication?
From the replication code, it seems to be the PacificA(http://research.microsoft.com/pubs/66814/tr-2008-25.pdf). Is this true?

As I known, the PacificA depends on a HA meta meta service to store the partition configuration. Is the current implements of meta service HA?

@imzhenyu
Copy link
Contributor

imzhenyu commented Jun 3, 2015

Nice digging, Ishmouse. You are right that the current protocol is largely following PacificA, with minor changes though. For meta server, we used to use a Microsoft internal Paxos library for production, but it is removed due to open source. Currently, the meta server supports durability, but not HA. We are evaluating ZooKeeper right now and will use it for HA of the meta server. Let me know if you have more questions.

Thanks,
Zhenyu

@lshmouse
Copy link
Author

lshmouse commented Jun 3, 2015

Thanks for your response~

@lshmouse lshmouse closed this as completed Jun 3, 2015
imzhenyu added a commit that referenced this issue Nov 12, 2015
Added interface for web server to query profiling data
imzhenyu pushed a commit that referenced this issue Nov 25, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants