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

Hadoop QA commented on HDFS-8551:
---------------------------------

\\
\\
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | pre-patch |  18m  7s | Pre-patch trunk compilation is 
healthy. |
| {color:green}+1{color} | @author |   0m  0s | The patch does not contain any 
@author tags. |
| {color:red}-1{color} | tests included |   0m  0s | The patch doesn't appear 
to include any new or modified tests.  Please justify why no new tests are 
needed for this patch. Also please list what manual steps were performed to 
verify this patch. |
| {color:green}+1{color} | javac |   7m 31s | There were no new javac warning 
messages. |
| {color:green}+1{color} | javadoc |   9m 37s | There were no new javadoc 
warning messages. |
| {color:green}+1{color} | release audit |   0m 23s | The applied patch does 
not increase the total number of release audit warnings. |
| {color:red}-1{color} | checkstyle |   2m 17s | The applied patch generated  2 
new checkstyle issues (total was 142, now 143). |
| {color:green}+1{color} | whitespace |   0m  0s | The patch has no lines that 
end in whitespace. |
| {color:green}+1{color} | install |   1m 35s | mvn install still works. |
| {color:green}+1{color} | eclipse:eclipse |   0m 32s | The patch built with 
eclipse:eclipse. |
| {color:green}+1{color} | findbugs |   3m 17s | The patch does not introduce 
any new Findbugs (version 3.0.0) warnings. |
| {color:green}+1{color} | native |   3m 14s | Pre-build of native portion |
| {color:green}+1{color} | hdfs tests | 162m  2s | Tests passed in hadoop-hdfs. 
|
| | | 208m 38s | |
\\
\\
|| Subsystem || Report/Notes ||
| Patch URL | 
http://issues.apache.org/jira/secure/attachment/12738221/HDFS-8551.patch |
| Optional Tests | javadoc javac unit findbugs checkstyle |
| git revision | trunk / b61b489 |
| checkstyle |  
https://builds.apache.org/job/PreCommit-HDFS-Build/11259/artifact/patchprocess/diffcheckstylehadoop-hdfs.txt
 |
| hadoop-hdfs test log | 
https://builds.apache.org/job/PreCommit-HDFS-Build/11259/artifact/patchprocess/testrun_hadoop-hdfs.txt
 |
| Test Results | 
https://builds.apache.org/job/PreCommit-HDFS-Build/11259/testReport/ |
| Java | 1.7.0_55 |
| uname | Linux asf909.gq1.ygridcore.net 3.13.0-36-lowlatency #63-Ubuntu SMP 
PREEMPT Wed Sep 3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux |
| Console output | 
https://builds.apache.org/job/PreCommit-HDFS-Build/11259/console |


This message was automatically generated.

> Fix hdfs datanode CLI usage message
> -----------------------------------
>
>                 Key: HDFS-8551
>                 URL: https://issues.apache.org/jira/browse/HDFS-8551
>             Project: Hadoop HDFS
>          Issue Type: Bug
>    Affects Versions: 2.6.0
>            Reporter: Xiaoyu Yao
>            Assignee: Brahma Reddy Battula
>         Attachments: HDFS-8551.patch
>
>
> There are two issues with current "hdfs datanode" usage message below.
> {code}
> Usage: java DataNode [-regular | -rollback]
>     -regular                 : Normal DataNode startup (default).
>     -rollback                : Rollback a standard or rolling upgrade.
>   Refer to HDFS documentation for the difference between standard
>   and rolling upgrades.
> {code}
> 1. "java DataNode" should be "hdfs datanode"
> 2. "rollingupgrace" option is missing but it is document correctly in the 
> [link|http://hadoop.apache.org/docs/r2.7.0/hadoop-project-dist/hadoop-hdfs/HDFSCommands.html#datanode].
> {code}
> Usage: hdfs datanode [-regular | -rollback | -rollingupgrace rollback]
> COMMAND_OPTION        Description
> -regular      Normal datanode startup (default).
> -rollback     Rollback the datanode to the previous version. This should be 
> used after stopping the datanode and distributing the old hadoop version.
> -rollingupgrade rollback      Rollback a rolling upgrade operation.
> {code}



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

Reply via email to