-
Notifications
You must be signed in to change notification settings - Fork 839
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
S3: ReadTimeoutException #954
Comments
Still see this after upgrading to 2.2.0. |
Yep, getting this as well. Had to ramp up my read timeout setting to some outrageous value, like 60 minutes. Also, there's another issue with netty, when multiple async requests are in progress: "server returned incomplete data". Kind of difficult to trigger, but it is there all right. |
Apologies for the delay. I was able to reproduce the error by uploading 400MB object with default configuration. All retry attempts failed. Investigating. |
I increased the Netty client
We will discuss and revisit the default configuration. Same request using |
@oakad Could you create another issue regarding the "server returned incomplete data" since it's a different issue? |
I had to switch back to v1 which has been very stable. You might want to review their timeout, etc setting for good defaults. |
@zoewangg I'm working on something else atm, but if and when I can trigger that error with a decent stack trace I will open the issue. As to the present issue, it is much easier to trigger it on a slow connection. I'd even say that it feels like read timeout is being measured from the start of upload (which would be incorrect). Rather, it will make more sense to monitor the connection for the upload progress being made and only engage the read timeout when waiting for server response. |
After investigating, this one was an issue of SDK use of netty Closing the issue, feel free to reopen if you have further questions. |
…60c6179c Pull request: release <- staging/c38a7134-93cb-4c57-a609-b36b60c6179c
When uploading large PDFs from S3 (hundreds of megabytes), I am seeing a timeout failure. It could be due to having configured some sanity timeouts, since I saw the client hang forever. I configured the client as below. I would expect the timeout of 15 minutes to be enough for file of this size.
The text was updated successfully, but these errors were encountered: