-
Notifications
You must be signed in to change notification settings - Fork 906
Increasing timeout in LambdaAsyncClient #2287
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
The timeout didn't change, or the api call is taking even more than 180 seconds?
|
We have one lambda that is triggered very rarely but execution takes ~60seconds. Thanks I will try this httpClient configuration! |
|
We have a small example in the Java SDK Dev Guide showing Netty-based HTTP Client configuration, but yes I think we can improve it. |
…9631a9a95 Pull request: release <- staging/c5637b12-8d27-47c5-94d8-71d9631a9a95
I was trying to increase timeout for
LambdaAsyncClient
unfortunately using builder I wasn't able to increase it.Describe the issue
I've tried to increase timeout by providing custom
ClientOverrideConfiguration
.Example code snippet in Scala:
When I deployed above changes unfortunately it seems that timeout didn't change and I'm still receiving:
Could anyone point me or tell how increasing socket/connection timeout should be done properly?
The text was updated successfully, but these errors were encountered: