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-8220) Hadoop install with yum timesout after 10 mins
Date Sat, 08 Nov 2014 06:26:33 GMT

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

Hudson commented on AMBARI-8220:
--------------------------------

SUCCESS: Integrated in Ambari-trunk-Commit #875 (See [https://builds.apache.org/job/Ambari-trunk-Commit/875/])
Revert "AMBARI-8220. Hadoop install with yum timesout after 10 mins (alejandro)" (yusaku:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=fc136f5e4f9724aadfe1e7437437032a0d739630)
* ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java
* ambari-agent/src/main/python/ambari_agent/PythonExecutor.py
* ambari-server/conf/unix/ambari.properties
* ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java


> Hadoop install with yum timesout after 10 mins
> ----------------------------------------------
>
>                 Key: AMBARI-8220
>                 URL: https://issues.apache.org/jira/browse/AMBARI-8220
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 1.7.0
>            Reporter: Alejandro Fernandez
>            Assignee: Alejandro Fernandez
>            Priority: Critical
>             Fix For: 1.7.0
>
>         Attachments: AMBARI-8220.patch
>
>
> Very often install fails due to timeout installing hadoop_2_2* packages, which can take
up to 8-12 mins.
> Each service has a metainfo.xml file that defines the timeout for each Component for
all types of actions (e.g., INSTALL, START, CONFIGURE, STOP).
> Ambari doesn't currently have a mechanism to set a different timeout just for the INSTALL
operation, so instead, the server side java code can do the following:
> Get the default agent timeout from the ambari.properties file (which will be increased
from 10 mins to 15 mins)
> Get the service component's timeout if it exists. If the operation is an INSTALL and
service component timeout is less than the default timeout, then use the default timeout.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message