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

Question: about the design choice over raft and others. #770

Open
phpstatic opened this issue Apr 23, 2020 · 0 comments
Open

Question: about the design choice over raft and others. #770

phpstatic opened this issue Apr 23, 2020 · 0 comments

Comments

@phpstatic
Copy link

phpstatic commented Apr 23, 2020

First of all I must say great work!!!

quinthar write this at Oct 19, 2016:

The Paxos is only used to elect the master (or re-elect if the master fails). Once a master is established, it coordinates all distributed transactions centrally, which is very fast.

My question is:

  • Is Raft able to do this job as fast as Paxos?
  • Is there any benefit that raft can't provide?
  • Is Bedrock still use Paxos only for elect the master?
  • I assume Bedrock use quorum vote to do the distributed transactions centrally
  • The commit logs store in sqlite or Log-Structured Merged-Tree ?
  • this projects use asynchronous with coroutine?

David Barrett provide some nice details. My question is :

  • The around network traffic between 6 server from 3 region average daily, and the peek bandwidth.

  • Bedrock only allow change schema when Cluster has one server(others leave and rejoin late), do you use some kind shard solution ? or just put all user data to one table ? or create new sqlite instance when users number over a certain amount( I assume this is allowed at Cluster mode)?

  • Can I use stored procedure without C++ ?

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

1 participant