-
Notifications
You must be signed in to change notification settings - Fork 240
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: Timeout modifies only the connection timeout #270
Comments
Yes, it’s an expected enhancement. So far only one timeout value, from my perspective, more tcp settings could be added as options beside those two timeouts. -yaguang From: Zoran Rajic [mailto:notifications@github.com] Specifying the timeout value in the S3 workload, ie: .. modifies only the socket connection timeout. Expectation:
— |
…d inactivity timeouts.
Hello Yaguang, It's good to know you were preparing the same enhancement. Apropos, the fix is trivial (see zoran-rajic@8f1de4c). Thanks, |
Hi Zoran, Could you pull your fix to upstream? -yaguang From: Zoran Rajic [mailto:notifications@github.com] Hello Yaguang, It's good to know you were preparing the same enhancement. Apropos, the fix is trivial (see zoran-rajic@8f1de4chttps://github.com/zoran-rajic/cosbench/commit/8f1de4c2b8c0f5aa4cf695a086d5bb66fec32659). Thanks, — |
Hi Yaguang, Created pull request @ #271 Thanks, |
Fix #270: S3 timeout parameter modifies both connection and inactivity timeouts
Specifying the timeout value in the S3 workload, ie:
.. modifies only the socket connection timeout.
Expectation:
The text was updated successfully, but these errors were encountered: