[
https://issues.apache.org/jira/browse/HDFS-7310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14201801#comment-14201801
]
Hadoop QA commented on HDFS-7310:
---------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12680093/HDFS-7310-003.patch
against trunk revision 61effcb.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 5 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-hdfs-project/hadoop-hdfs.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/8688//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/8688//console
This message is automatically generated.
> Mover can give first priority to local DN if it has target storage type
> available in local DN
> ---------------------------------------------------------------------------------------------
>
> Key: HDFS-7310
> URL: https://issues.apache.org/jira/browse/HDFS-7310
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: balancer & mover
> Affects Versions: 3.0.0
> Reporter: Uma Maheswara Rao G
> Assignee: Vinayakumar B
> Attachments: HDFS-7310-001.patch, HDFS-7310-002.patch,
> HDFS-7310-003.patch
>
>
> Currently Mover logic may move blocks to any DN which had target storage
> type. But if the src DN has target storage type then mover can give highest
> priority to local DN. If local DN does not contains target storage type, then
> it can assign to any DN as the current logic does.
> This is a thought, have not go through the code fully yet.
> Thoughts?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
