dengsc created HDFS-13905: ----------------------------- Summary: HDFS NameNode jmx information inaccuracy Key: HDFS-13905 URL: https://issues.apache.org/jira/browse/HDFS-13905 Project: Hadoop HDFS Issue Type: Bug Components: nn Reporter: dengsc
The information obtained using Namenode jmx does not match the actual situation。 jmx json data: {code:java} // http://{namenode_ip}:50070/jmx/?qry=Hadoop:service=NameNode,name=BlockStats { "beans" : [ { "name" : "Hadoop:service=NameNode,name=BlockStats", "modelerType" : "org.apache.hadoop.hdfs.server.blockmanagement.BlockManager", "StorageTypeStats" : [ { "key" : "ARCHIVE", "value" : { "blockPoolUsed" : 10411907414335294, "capacityRemaining" : 1435938815980942, "capacityTotal" : 11851673443205120, "capacityUsed" : 10411907414335294, "nodesInService" : 111 } }, { "key" : "DISK", "value" : { "blockPoolUsed" : 16789505803398474, "capacityRemaining" : 3404376930515479, "capacityTotal" : 20204114325184512, "capacityUsed" : 16789505803398474, "nodesInService" : 473 } } ] } ] } {code} but ,in our cluster : disk nodesInService = 462 archive nodesInService = 110 -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org