Added random latency to SQS receives. #198
Merged
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.
Latency is based on the inclusion of two environment variables
(
GOAWS_RANDOM_LATENCY_MIN
andGOAWS_RANDOM_LATENCY_MAX
), which, if setwill prevent messages from being released from the queue until after a
period of random, simulated latency has elapsed.
The purpose of this change is to aid in local testing against AWS when
SQS latency is expected and needs to be developed against.