-
Notifications
You must be signed in to change notification settings - Fork 44
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
Gossip block dissemination re-architecture #49
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: yacovm <[email protected]>
Signed-off-by: yacovm <[email protected]>
Signed-off-by: yacovm <[email protected]>
Signed-off-by: yacovm <[email protected]>
Signed-off-by: yacovm <[email protected]>
Signed-off-by: yacovm <[email protected]>
Signed-off-by: yacovm <[email protected]>
|
||
The proposal is to be implemented in two phases: | ||
|
||
**Phase I**: Gossip block replication among peers will cease to operate, and the relevant code will be removed. This means that both gossip block replication layer and leader election layers will be removed and each peer will always pull only from the ordering service. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Question here:
Assuming we have 5 peers(from different org) and 5 orderers(running in raft).
Will those 5 peers pull block from raft leader or those 5 peers able to pull block from one of orderer nodes randomly?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The peers don't know who is the leader anyway, so they have to use an arbitrary node
Will newly joined nodes be affected when they perform block synchronization? |
No description provided.