[HDFS-13905] HDFS NameNode jmx information inaccuracy

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: nn
• Target Version/s: 2.6.0
• Assignee: Unassigned
• Reporter: dengsc
• Created: 10/Sep/18 05:56
• Updated: 10/Sep/18 05:56

Description

The information obtained using Namenode jmx does not match the actual situation。

jmx json data:

// 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
      }
    } ]
  } ]
}

but ，in our cluster :

disk nodesInService = 462

archive nodesInService = 110