You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-dev@hadoop.apache.org by "Brandon Li (Created) (JIRA)" <ji...@apache.org> on 2012/03/15 02:14:38 UTC
[jira] [Created] (HDFS-3095) namenode format should not create
stroage dir if it's doesn't exist
namenode format should not create stroage dir if it's doesn't exist
--------------------------------------------------------------------
Key: HDFS-3095
URL: https://issues.apache.org/jira/browse/HDFS-3095
Project: Hadoop HDFS
Issue Type: Bug
Components: name-node
Affects Versions: 0.24.0
Reporter: Brandon Li
Assignee: Brandon Li
The storage directory can be a mount point.
Automatically creating the mount point could be problematic.
--
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
[jira] [Resolved] (HDFS-3095) Namenode format should not create the
storage directory if it doesn't exist
Posted by "Brandon Li (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HDFS-3095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brandon Li resolved HDFS-3095.
------------------------------
Resolution: Invalid
Release Note:
Todd made a point here.
HDFS user should not have write permission beyond mount points.
> Namenode format should not create the storage directory if it doesn't exist
> ----------------------------------------------------------------------------
>
> Key: HDFS-3095
> URL: https://issues.apache.org/jira/browse/HDFS-3095
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: name-node
> Affects Versions: 0.24.0, 1.1.0
> Reporter: Brandon Li
> Assignee: Brandon Li
>
> The storage directory can be a mount point.
> Automatically creating the mount point could be problematic.
--
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