[LOGGING_4864] Consider timeout errors and add logging debug statements #39
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.
Description
A customer notified us that the retry mechanism was not properly considering
TimeoutError
s, and even opened a ticket suggesting a solution. After inspecting the issue, we found that what was really performing the timeout was theClientSession
established for the whole lambda execution, which was set to tool low (3 seconds, I wonder if it was meant to be 30 instead). This PR fixes this issue by:Related ticket(s)
https://newrelic.atlassian.net/browse/LOGGING-4864
https://newrelic.atlassian.net/browse/LOGGING-4700
Tests