[
https://issues.apache.org/jira/browse/AMBARI-14479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15074192#comment-15074192
]
Hudson commented on AMBARI-14479:
---------------------------------
ABORTED: Integrated in Ambari-trunk-Commit #4104 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/4104/])
AMBARI-14479. Namenode start fails when time taken to get out of (dlysnichenko:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=376fc6ffccab683b9f83f825762e0ef2efaf0d82])
*
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py
*
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_namenode.py
* ambari-server/src/test/python/stacks/2.0.6/HDFS/test_namenode.py
> Namenode start fails when time taken to get out of safemode is more than 20
> minutes.
> ------------------------------------------------------------------------------------
>
> Key: AMBARI-14479
> URL: https://issues.apache.org/jira/browse/AMBARI-14479
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.1.2
> Reporter: Dmitry Lysnichenko
> Assignee: Dmitry Lysnichenko
> Fix For: 2.2.1
>
> Attachments: AMBARI-14479.patch
>
>
> Issue
> Namenode safemode check timeout value of 30mins is more than the server
> timeout of 20mins for a task. Hence, the server kills the namenode startup
> script if it takes more than 20mins to get out of safemode.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
