Skip to content
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

Investigate increasing CURLOPT_LOW_SPEED_TIME for calls which do not send data #2174

Open
JustinKyleJames opened this issue Nov 17, 2022 · 3 comments

Comments

@JustinKyleJames
Copy link
Contributor

Some calls do not transfer data but may take time for the S3 provider to handle. One notable one is the S3_copy_object call.

We set this parameter to 15 seconds if the main timeout is set to 0 (no timeout). That may not be long enough for some providers.

There are two options:

  1. Simple increase the time for CURLOPT_LOW_SPEED_TIME.
  2. Use the default of 0 for CURLOPT_LOW_SPEED_TIME in this case.

The second option seems consistent with the desire to not have timeouts. However, this could possibly result in a situation where a call hangs indefinitely or waits for some type of transport timeout.

@trel
Copy link
Member

trel commented Dec 1, 2023

Have we seen this occur with any particular S3 provider or appliance? Or with an object of a certain large size?

@alanking
Copy link
Contributor

Now that the S3 resource plugin has absorbed this project, I think we should transfer this issue. Thoughts?

@trel
Copy link
Member

trel commented Feb 23, 2024

yes please

@alanking alanking transferred this issue from irods/libs3 Feb 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

3 participants