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 "Mostafa Elhemali (JIRA)" <ji...@apache.org> on 2013/01/17 00:56:12 UTC

[jira] [Created] (HDFS-4413) Secondary namenode won't start if HDFS isn't the default file system

Mostafa Elhemali created HDFS-4413:
--------------------------------------

             Summary: Secondary namenode won't start if HDFS isn't the default file system
                 Key: HDFS-4413
                 URL: https://issues.apache.org/jira/browse/HDFS-4413
             Project: Hadoop HDFS
          Issue Type: Bug
            Reporter: Mostafa Elhemali


If HDFS is not the default file system (fs.default.name is something other than hdfs://...), then secondary namenode throws early on in its initialization. This is a needless check as far as I can tell, and blocks scenarios where HDFS services are up but HDFS is not the default file system.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira