This repository has been archived by the owner on Aug 2, 2021. It is now read-only.
swarm-smoke: fix check max prox hosts for pull/push sync modes #1578
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.
This PR is adding a flag to specify the kind of smoke test to test for with respect to syncing:
pullsync
- make sure that all chunks are hosted at all max prox hosts - previously we had a more relaxed version, where we were checking only one of the max prox hosts (if there were multiple)pushsync
- make sure that all chunks are found at at least one max prox host - we don't know which node received our chunk, and sent back a receipt, it can be any one of the max prox hosts if there are multipleboth
- same as 1.It also adds a flag to specify if we want to wait for
pushsync
orpullsync
to complete. Uploads attach atag
, so that we can monitor thepushsync
until completion.