[
https://issues.apache.org/jira/browse/HADOOP-2447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12553427
]
dhruba borthakur commented on HADOOP-2447:
------------------------------------------
It is a very good idea to print these statistics in the webui. I will go ahead
and do that. Also, it might be a good idea to add this to the "dfsadmin
-report" command too.
At this time, I do not plan on adding a command line utility to change this
dfs.max.objects on a running namenode. If an administrator wants to change this
config parameter, the namenode has to be restarted. This is true for most other
existing-namenode-parameters and I do not want to introduce a special command
just to change this dfs.max.objects parameter.
> HDFS should be capable of limiting the total number of inodes in the system
> ---------------------------------------------------------------------------
>
> Key: HADOOP-2447
> URL: https://issues.apache.org/jira/browse/HADOOP-2447
> Project: Hadoop
> Issue Type: New Feature
> Reporter: Sameer Paranjpye
> Assignee: dhruba borthakur
> Fix For: 0.16.0
>
> Attachments: fileLimit.patch
>
>
> The HDFS Namenode should be capable of limiting the total number of Inodes
> (files + directories). The can be done through a config variable, settable in
> hadoop-site.xml. The default should be no limit.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
