ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-14479) Namenode start fails when time taken to get out of safemode is more than 20 minutes.
Date Tue, 29 Dec 2015 14:50:49 GMT

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

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

SUCCESS: Integrated in Ambari-branch-2.2 #121 (See [https://builds.apache.org/job/Ambari-branch-2.2/121/])
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=305e67be76e7cfc5f594b3e3c10887b7c5bfcfd1])
* 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)

Mime
View raw message