[
https://issues.apache.org/jira/browse/HADOOP-13600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15704351#comment-15704351
]
Sahil Takiar commented on HADOOP-13600:
---------------------------------------
Will take a look at HADOOP-13823
Addressed a few of the comments:
* Using a {{BlockingQueue}} to track keys that need to be deleted
* A separate thread takes from the queue until it taken
{{MAX_ENTRIES_TO_DELETE}} keys, and then it issues the DELETE request
* An {{AtomicBoolean}} is passed into the {{ProgressListener}} of the COPY
request, if the COPY fails the boolean is set to false, in which case no more
COPY requests will be issued
* [[email protected]] I took a look at your PR, is it necessary to have a
threadpool where each thread calls {{Copy.waitForCopyResult()}}; would it be
simpler to create a separate {{TransferManager}} just for COPY requests
> S3a rename() to copy files in a directory in parallel
> -----------------------------------------------------
>
> Key: HADOOP-13600
> URL: https://issues.apache.org/jira/browse/HADOOP-13600
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 2.7.3
> Reporter: Steve Loughran
> Assignee: Steve Loughran
>
> Currently a directory rename does a one-by-one copy, making the request
> O(files * data). If the copy operations were launched in parallel, the
> duration of the copy may be reducable to the duration of the longest copy.
> For a directory with many files, this will be significant
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
