You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2015/12/23 16:27:46 UTC

[jira] [Commented] (AMBARI-14479) Namenode start fails when time taken to get out of safemode is more than 20 minutes.

    [ https://issues.apache.org/jira/browse/AMBARI-14479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15069741#comment-15069741 ] 

Hudson commented on AMBARI-14479:
---------------------------------

SUCCESS: Integrated in Ambari-branch-2.2 #100 (See [https://builds.apache.org/job/Ambari-branch-2.2/100/])
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=59d7a3464317d03f1a9a1594e80f4d9edb7ad011])
* ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py
* ambari-server/src/test/python/stacks/2.0.6/HDFS/test_namenode.py
* ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_namenode.py
* ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/metainfo.xml


> 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.1.2
>
>         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)