You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When making very long duration requests, such as a lambda invoke that takes over 5 minutes to complete, the SDK may eventually timeout even if the response completes because the socket is not kept alive.
A current workaround seems to have fixed this issue for an internal customer, so we should add a socket.setKeepAlive call to the Node.js HTTP request.
Describe the bug
When making very long duration requests, such as a lambda invoke that takes over 5 minutes to complete, the SDK may eventually timeout even if the response completes because the socket is not kept alive.
A current workaround seems to have fixed this issue for an internal customer, so we should add a
socket.setKeepAlive
call to the Node.js HTTP request.Expected Behavior
long request >5 min completes
Current Behavior
long request >5 min reports a timeout even if the server completes the request successfully
Reproduction Steps
invoke a lambda transaction that takes a long time, 5-15 minutes.
Possible Solution
add
socket.setKeepAlive(true, xxx)
somewhere in the request creation processAdditional Information/Context
No response
SDK version used
current
Environment details (OS name and version, etc.)
EC2 to Lambda
The text was updated successfully, but these errors were encountered: