Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
#4589
Analysed recent errors in gatway integration tests. There is one error everywhere (I hope it is the last one).
The problem is that after restarting orderer2 peer did not manage to reconnect to it because of backoff timeout.
I studied the logs and made it so that we don't send Submit until the peer connects to orderer2.
The mechanics of waiting are as follows:
For a test this is ok, but maybe in real work it will not work. Then I suggest someone to modify the file
github.com/hyperledger/fabric/internal/pkg/gateway/registry.go
. When selecting connections orderers should check the connection status and reconnect violently if necessary.