hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-13600) S3a rename() to copy files in a directory in parallel
Date Mon, 12 Dec 2016 22:38:58 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-13600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15743379#comment-15743379

ASF GitHub Bot commented on HADOOP-13600:

Github user thodemoor commented on a diff in the pull request:

    --- Diff: hadoop-tools/hadoop-aws/src/main/java/org/apache/hadoop/fs/s3a/S3AFileSystem.java
    @@ -207,11 +218,17 @@ public StorageStatistics provide() {
           long keepAliveTime = longOption(conf, KEEPALIVE_TIME,
               DEFAULT_KEEPALIVE_TIME, 0);
    -      threadPoolExecutor = BlockingThreadPoolExecutorService.newInstance(
    +      uploadThreadPoolExecutor = BlockingThreadPoolExecutorService.newInstance(
               maxThreads + totalTasks,
               keepAliveTime, TimeUnit.SECONDS,
    -          "s3a-transfer-shared");
    +          "s3a-upload-shared");
    +      copyThreadPoolExecutor = BlockingThreadPoolExecutorService.newInstance(
    +          maxThreads,
    --- End diff --
    COPY is server-side (no data transfer) and is thus generally much less resource-intensive
and much quicker than PUT (the smaller your bandwidth to S3, the bigger the difference becomes).
So I think the `maxThreads` for the copyThreadpool could be (much) higher than for uploadThreadpool
and should thus be configurable separately.

> 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: Sahil Takiar
> 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

To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org

View raw message