-
Notifications
You must be signed in to change notification settings - Fork 8.9k
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
[FAB-17539] Always remember anchor peers in membership #1422
Conversation
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.
Hi Wenjian.
I did only a quick overview and I see that:
- Lock is missing, see comment
- No integration test yet, I guess this is a WIP so let's wait for that
- You didn't add this to core.yaml yet, so let's do that too.
0aa08fd
to
fabbac9
Compare
@yacovm I have addressed your comments. However, there were UT/IT failures (may be flakes). |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
f2e7af3
to
3671d42
Compare
Gossip service removes a peer from its membership if the peer's alive message is expired. However, it should always remember the anchor peers and bootstrap peers in order for the peer to reconnect. Gossip already remembers bootstrap peers. This PR adds code to track all anchor peers' endpoints and updates the expiration callback function to not delete anchor peers. Signed-off-by: Wenjian Qiao <wenjianq@gmail.com>
Hit gossip CI flake https://jira.hyperledger.org/browse/FAB-17451, problem 1)
|
/ci-run |
) Gossip service removes a peer from its membership if the peer's alive message is expired. However, it should always remember the anchor peers and bootstrap peers in order for the peer to reconnect. Gossip already remembers bootstrap peers. This PR adds code to track all anchor peers' endpoints and updates the expiration callback function to not delete anchor peers. Signed-off-by: Wenjian Qiao <wenjianq@gmail.com>
Backport to release-1.4 via PR #1815 |
) Gossip service removes a peer from its membership if the peer's alive message is expired. However, it should always remember the anchor peers and bootstrap peers in order for the peer to reconnect. Gossip already remembers bootstrap peers. This PR adds code to track all anchor peers' endpoints and updates the expiration callback function to not delete anchor peers. Signed-off-by: Wenjian Qiao <wenjianq@gmail.com>
Gossip service removes a peer from its membership if the peer's alive message is expired. However, it should always remember the anchor peers and bootstrap peers in order for the peer to reconnect. Gossip already remembers bootstrap peers. This PR adds code to track all anchor peers' endpoints and updates the expiration callback function to not delete anchor peers. Signed-off-by: Wenjian Qiao <wenjianq@gmail.com>
) (hyperledger#1815) Gossip service removes a peer from its membership if the peer's alive message is expired. However, it should always remember the anchor peers and bootstrap peers in order for the peer to reconnect. Gossip already remembers bootstrap peers. This PR adds code to track all anchor peers' endpoints and updates the expiration callback function to not delete anchor peers. Signed-off-by: Wenjian Qiao <wenjianq@gmail.com> # Conflicts: # gossip/service/gossip_service_test.go
Signed-off-by: Wenjian Qiao wenjianq@gmail.com
Type of change
Description
Gossip service removes a peer from its membership if the peer's alive message is expired.
However, it should not remove the anchor peers or bootstrap peers in order for
the peer to reconnect. Gossip already remembers bootstrap peers. This PR adds code to track
all anchor peers' endpoints and updates the expiration callback function to not delete
anchor peers.
Additional details
Related issues
https://jira.hyperledger.org/browse/FAB-17539