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

ASF GitHub Bot commented on HADOOP-15887:
-----------------------------------------

github-actions[bot] commented on PR #1794:
URL: https://github.com/apache/hadoop/pull/1794#issuecomment-3652444685

   We're closing this stale PR because it has been open for 100 days with no 
activity. This isn't a judgement on the merit of the PR in any way. It's just a 
way of keeping the PR queue manageable.
   If you feel like this was a mistake, or you would like to continue working 
on it, please feel free to re-open it and ask for a committer to remove the 
stale tag and review again.
   Thanks all for your contribution.




> Add an option to avoid writing data locally in Distcp
> -----------------------------------------------------
>
>                 Key: HADOOP-15887
>                 URL: https://issues.apache.org/jira/browse/HADOOP-15887
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: tools/distcp
>    Affects Versions: 2.8.2, 3.0.0
>            Reporter: Tao Jie
>            Assignee: Tao Jie
>            Priority: Major
>         Attachments: HADOOP-15887.001.patch, HADOOP-15887.002.patch, 
> HADOOP-15887.003.patch, HADOOP-15887.004.patch, HADOOP-15887.005.patch
>
>
> When copying large amount of data from one cluster to another via Distcp, and 
> the Distcp jobs run in the target cluster, the datanode local usage would be 
> imbalanced. Because the default placement policy chooses the local node to 
> store the first replication.
> In https://issues.apache.org/jira/browse/HDFS-3702 we add a flag in DFSClient 
> to avoid replicating to the local datanode.  We can make use of this flag in 
> Distcp.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to