Increase rabbitMQ consumer timeout to one hour. #745
Merged
Conversation
This file contains hidden or 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
During IDAP 200Gb challenge testing we found that very large datasets can take longer than 30 minutes to report from the DID finder back to the app. There is a default setting of 1/2 hour for a message to be ack-ed before closing the channel and putting the message back in the queue. Increasing this value to 1 hour to avoid this problem.
|
While this would prevent the issue we had last night (it took ~45 minutes), we did only one dataset that has 64k files. We will need to process 210k+ dataset files so just changing to 60 min won't really help. |
|
I'm going to merge this just so we can find this later if it comes up again |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
During IDAP 200Gb challenge testing we found that very large datasets can take longer than 30 minutes to report from the DID finder back to the app. There is a default setting of 1/2 hour for a message to be ack-ed before closing the channel and putting the message back in the queue.
Increasing this value to 1 hour to avoid this problem.