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

Static leader should not give up on retrieving blocks #507

Merged
merged 1 commit into from
Jan 16, 2020

Conversation

wlahti
Copy link
Contributor

@wlahti wlahti commented Jan 16, 2020

Type of change

  • Bug fix

Description

When a peer is configured as a static org leader for gossip, it should
not give up on retrieving blocks in the event that the orderering
service goes down for an extended period of time (i.e. longer than the
peer.deliveryclient.reconnectTotalTimeThreshold). Otherwise, the peer
must be restarted before it will act as the leader again.

Related issues

FAB-17327

When a peer is configured as a static org leader for gossip, it should
not give up on retrieving blocks in the event that the orderering
service goes down for an extended period of time (i.e. longer than the
peer.deliveryclient.reconnectTotalTimeThreshold). Otherwise, the peer
must be restarted before it will act as the leader again.

FAB-17327

Signed-off-by: Brett Logan <brett.t.logan@ibm.com>
Signed-off-by: Will Lahti <wtlahti@us.ibm.com>
@wlahti wlahti requested a review from a team as a code owner January 16, 2020 18:03
@yacovm yacovm merged commit 470f133 into hyperledger:master Jan 16, 2020
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.

None yet

3 participants