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

Posted to dev@ambari.apache.org by "Sumit Mohanty (JIRA)" <ji...@apache.org> on 2013/09/27 23:24:08 UTC

[jira] [Resolved] (AMBARI-3370) Secondary NameNode does not start after install. Missing local folder.

     [ https://issues.apache.org/jira/browse/AMBARI-3370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sumit Mohanty resolved AMBARI-3370.
-----------------------------------

    Resolution: Fixed

committed to branch-1.4.1 and trunk
                
> Secondary NameNode does not start after install. Missing local folder.
> ----------------------------------------------------------------------
>
>                 Key: AMBARI-3370
>                 URL: https://issues.apache.org/jira/browse/AMBARI-3370
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: 1.4.1
>            Reporter: Sumit Mohanty
>            Assignee: Sumit Mohanty
>             Fix For: 1.4.1
>
>         Attachments: AMBARI-3370.patch
>
>
> The following properties moved to hdfs-site from core-site.
> dfs.namenode.checkpoint.edits.dir
> dfs.namenode.checkpoint.dir
> dfs.namenode.checkpoint.period
> The agent code needs to be changed to lookup these properties at hdfs-site.

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