You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "dhruba borthakur (JIRA)" <ji...@apache.org> on 2007/12/18 20:55:43 UTC

[jira] Commented: (HADOOP-2447) HDFS should be capable of limiting the total number of inodes in the system

    [ https://issues.apache.org/jira/browse/HADOOP-2447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12552874 ] 

dhruba borthakur commented on HADOOP-2447:
------------------------------------------

My proposal is to have dfs.max.objects as a parameter in the configuration. It is a hard limit on the number of files + + directories + blocks that dfs namenode can support. If the namenode exceeds this limit, then creations of files/directories and allocations of new blocks will fail.


> 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
>
>
> 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.