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

Hadoop QA commented on HDFS-11825:
----------------------------------

| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m 
16s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} @author {color} | {color:green}  0m  
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
|| || || || {color:brown} trunk Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 12m 
30s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} shadedclient {color} | {color:green} 
20m 40s{color} | {color:green} branch has no errors when building and testing 
our client artifacts. {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green}  0m 
 0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} shadedclient {color} | {color:green}  
9m 40s{color} | {color:green} patch has no errors when building and testing our 
client artifacts. {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green}  0m 
14s{color} | {color:green} The patch does not generate ASF License warnings. 
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 31m  5s{color} | 
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker |  Image:yetus/hadoop:71bbb86 |
| JIRA Issue | HDFS-11825 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12868173/HADOOP-11825.1.patch |
| Optional Tests |  asflicense  shadedclient  |
| uname | Linux aa3655742cd4 4.4.0-43-generic #63-Ubuntu SMP Wed Oct 12 
13:48:03 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | /testptch/hadoop/patchprocess/precommit/personality/provided.sh 
|
| git revision | trunk / 6f789fe |
| modules | C: hadoop-hdfs-project/hadoop-hdfs U: 
hadoop-hdfs-project/hadoop-hdfs |
| Console output | 
https://builds.apache.org/job/PreCommit-HDFS-Build/21414/console |
| Powered by | Apache Yetus 0.6.0-SNAPSHOT   http://yetus.apache.org |


This message was automatically generated.



> Make dfshealth datanode information more readable
> -------------------------------------------------
>
>                 Key: HDFS-11825
>                 URL: https://issues.apache.org/jira/browse/HDFS-11825
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: hdfs
>    Affects Versions: 3.0.0-alpha2
>            Reporter: Sarah Victor
>            Assignee: Sarah Victor
>            Priority: Trivial
>         Attachments: HADOOP-11825.1.patch
>
>
> On the dfshealth.html#tab-datanode web page to monitor health of Hadoop nodes 
> (hadoop-hdfs-project/hadoop-hdfs/src/main/webapps/hdfs/dfshealth.html)
> (1) The Capacity column reports the node capacity but is sorted by another 
> value that is not reported (ie) the % Capacity Used. It will be good to name 
> the column heading as "Capacity Used [%]" and report both the Capacity Used 
> and the Capacity Used %
> (2) The Block Pool Used column reports the block pools used but is sorted by 
> the % Block Pool Used, It will be good to name the column heading as Block 
> Pool Used [%]
> (3) The "Last contact" column is more easily understood if we call it "Last 
> Heartbeat". Adding the measurement unit [secs] to the header makes it more 
> easily understood.
> (3) Adding the measurement unit [mins] to the "Last Block Report" header 
> makes it more easily understood.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

Reply via email to