-
Notifications
You must be signed in to change notification settings - Fork 8.9k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add flow control to SYNC_STATE_SNAPSHOT
This patch changes the peer snapshot retrieval logic from a non-blocking channel write to a blocking channel write with a timeout. This allows gRPC's own buffering mechanisms to apply back pressure when sending large state snapshots. Additionally, this change will suppress some of the spammy log messages which can flood logs when the correlation id gets out of sync. https://jira.hyperledger.org/browse/FAB-380 Change-Id: Icc3d37f2d161f6ac0bae984ca43e2286a45fbb3d Signed-off-by: Jason Yellick <jyellick@us.ibm.com>
- Loading branch information
Jason Yellick
committed
Sep 14, 2016
1 parent
7b2e488
commit 62d866d
Showing
5 changed files
with
50 additions
and
11 deletions.
There are no files selected for viewing
18 changes: 18 additions & 0 deletions
18
bddtests/bdd-docker/docker-compose-4-consensus-batch-nosnapshotbuffer.yml
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,18 @@ | ||
vp0: | ||
environment: | ||
# The combination of the following two environment variables ensures that a state snapshot will be pulled | ||
# and that the state snapshot buffer will be exhausted | ||
- CORE_PEER_SYNC_STATE_SNAPSHOT_CHANNELSIZE=0 | ||
- CORE_STATETRANSFER_MAXDELTAS=1 | ||
vp1: | ||
environment: | ||
- CORE_PEER_SYNC_STATE_SNAPSHOT_CHANNELSIZE=0 | ||
- CORE_STATETRANSFER_MAXDELTAS=1 | ||
vp2: | ||
environment: | ||
- CORE_PEER_SYNC_STATE_SNAPSHOT_CHANNELSIZE=0 | ||
- CORE_STATETRANSFER_MAXDELTAS=1 | ||
vp3: | ||
environment: | ||
- CORE_PEER_SYNC_STATE_SNAPSHOT_CHANNELSIZE=0 | ||
- CORE_STATETRANSFER_MAXDELTAS=1 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters