[
https://issues.apache.org/jira/browse/HDFS-4413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13708168#comment-13708168
]
Matt Foley commented on HDFS-4413:
----------------------------------
Changed the TargetVersion from 1.2.1 to 1.2.0, recognizing that it did in fact
go out in 1.2.0, so should be consistent with FixVersion.
> 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
> Components: namenode
> Affects Versions: 1-win, 1.2.1
> Reporter: Mostafa Elhemali
> Assignee: Mostafa Elhemali
> Fix For: 1.2.0
>
> Attachments: HDFS-4413.branch-1.patch
>
>
> 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
