hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Haohui Mai (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-6180) dead node count / listing is very broken in JMX and old GUI
Date Thu, 17 Apr 2014 18:47:19 GMT

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

Haohui Mai commented on HDFS-6180:
----------------------------------

The reason why I removed this test is that {{--registration-name--}} is not a valid DNS name.
Things like GetBlockLocations, WebHDFS, and DataNodeManager assume that host name is a valid
DNS name. For example, WebHDFS uses the hostname to generate the URI pointing to the DN, thus
the test might be invalid at the first place. What we probably should have done is to make
this assumption explicit.

To test the case where the user puts a DNS name in the include list, the code in {{testIncludeExcludeLists}}
adds {{localhost}} (which is usually the only valid DNS name in test environment) into the
include lists and verifies that the {{DatanodeManager}} recognizes it.

> dead node count / listing is very broken in JMX and old GUI
> -----------------------------------------------------------
>
>                 Key: HDFS-6180
>                 URL: https://issues.apache.org/jira/browse/HDFS-6180
>             Project: Hadoop HDFS
>          Issue Type: Bug
>    Affects Versions: 2.3.0
>            Reporter: Travis Thompson
>            Assignee: Haohui Mai
>            Priority: Blocker
>             Fix For: 2.5.0
>
>         Attachments: HDFS-6180.000.patch, HDFS-6180.001.patch, HDFS-6180.002.patch, HDFS-6180.003.patch,
HDFS-6180.004.patch, dn.log
>
>
> After bringing up a 578 node cluster with 13 dead nodes, 0 were reported on the new GUI,
but showed up properly in the datanodes tab.  Some nodes are also being double reported in
the deadnode and inservice section (22 show up dead, 565 show up alive, 9 duplicated nodes).

> From /jmx (confirmed that it's the same in jconsole):
> {noformat}
> {
>     "name" : "Hadoop:service=NameNode,name=FSNamesystemState",
>     "modelerType" : "org.apache.hadoop.hdfs.server.namenode.FSNamesystem",
>     "CapacityTotal" : 5477748687372288,
>     "CapacityUsed" : 24825720407,
>     "CapacityRemaining" : 5477723861651881,
>     "TotalLoad" : 565,
>     "SnapshotStats" : "{\"SnapshottableDirectories\":0,\"Snapshots\":0}",
>     "BlocksTotal" : 21065,
>     "MaxObjects" : 0,
>     "FilesTotal" : 25454,
>     "PendingReplicationBlocks" : 0,
>     "UnderReplicatedBlocks" : 0,
>     "ScheduledReplicationBlocks" : 0,
>     "FSState" : "Operational",
>     "NumLiveDataNodes" : 565,
>     "NumDeadDataNodes" : 0,
>     "NumDecomLiveDataNodes" : 0,
>     "NumDecomDeadDataNodes" : 0,
>     "NumDecommissioningDataNodes" : 0,
>     "NumStaleDataNodes" : 1
>   },
> {noformat}
> I'm not going to include deadnode/livenodes because the list is huge, but I've confirmed
there are 9 nodes showing up in both deadnodes and livenodes.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message