[
https://issues.apache.org/jira/browse/HDFS-300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J resolved HDFS-300.
--------------------------
Resolution: Not A Problem
Not a problem anymore (perhaps since branch-0.20-security pick up).
>From a sample /jmx metrics output:
{code}
{
"name" : "hadoop:service=NameNode,name=FSNamesystemState",
"modelerType" : "org.apache.hadoop.hdfs.server.namenode.FSNamesystem",
"CapacityTotal" : 999527776256,
"CapacityUsed" : 413696,
"CapacityRemaining" : 732080799744,
"TotalLoad" : 1,
"BlocksTotal" : 29,
"FilesTotal" : 70,
"PendingReplicationBlocks" : 0,
"UnderReplicatedBlocks" : 0,
"ScheduledReplicationBlocks" : 0,
"FSState" : "safeMode"
}
{code}
*"BlocksTotal" : 29*
*"FilesTotal" : 70*
> NameNode to blat total number of files and blocks
> -------------------------------------------------
>
> Key: HDFS-300
> URL: https://issues.apache.org/jira/browse/HDFS-300
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: Marco Nicosia
> Priority: Minor
>
> Right now, the namenode reports lots of rates (block read per sec, removed
> per sec, etc etc) but it doesn't actually report how many files and blocks
> total exist in the system. It'd be great if we could have this, so that our
> reporting systems can show the growth trends over time.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
