hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-9720) DiskBalancer : Add configuration parameters
Date Mon, 28 Mar 2016 17:53:25 GMT

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

Hadoop QA commented on HDFS-9720:
---------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 0s {color} | {color:blue}
Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 8s {color} | {color:red}
HDFS-9720 does not apply to HDFS-1312. Rebase required? Wrong Branch? See https://wiki.apache.org/hadoop/HowToContribute
for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/12785042/HDFS-9720-HDFS-1312.001.patch
|
| JIRA Issue | HDFS-9720 |
| Console output | https://builds.apache.org/job/PreCommit-HDFS-Build/14960/console |
| Powered by | Apache Yetus 0.2.0   http://yetus.apache.org |


This message was automatically generated.



> DiskBalancer : Add configuration parameters
> -------------------------------------------
>
>                 Key: HDFS-9720
>                 URL: https://issues.apache.org/jira/browse/HDFS-9720
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: balancer & mover
>    Affects Versions: HDFS-1312
>            Reporter: Anu Engineer
>            Assignee: Anu Engineer
>             Fix For: HDFS-1312
>
>         Attachments: HDFS-9720-HDFS-1312.001.patch
>
>
> Add the following config params:
> # Max Disk Throughput - This allows users to control how much disk I/O is generated while
disk balancer is running
> # Max Disk Errors - For each move operation, this allows user to specify how many I/O
failures are tolerated before we declare the operation as failed.
> #Block Tolerance - Specifies how much movement of data is good enough. since the datanodes
are active while the copy is going on, tolerance lets the user specify that if we reached
something like 5% of projected Ideal storage on the destination disk, we can consider that
move to be successful.
> Each of these parameter can be specified for each MoveStep. if not specified then the
config parameters are used.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message