Details
-
Task
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
Description
We use the AWS SDK async APIs in some places in S3FileSystem, but all they do is spawn a separate thread and run the sync API in it.
Instead we should use our IO executor, which would:
1) put an upper bound on the number of threads started
2) (presumably) reduce latency by reusing threads instead of spawning a throwaway thread for each async call
3) allow for cancellation
Attachments
Issue Links
- links to