Skip to content

Conversation

yacovm
Copy link
Contributor

@yacovm yacovm commented Feb 3, 2022

No description provided.

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.
Copy link
Contributor

@SamYuan1990 SamYuan1990 Feb 3, 2022

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?

Copy link
Contributor Author

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

@hxx258456
Copy link

Will newly joined nodes be affected when they perform block synchronization?

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

Successfully merging this pull request may close these issues.

3 participants