You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Alejandro Fernandez (JIRA)" <ji...@apache.org> on 2014/11/08 00:31:34 UTC

[jira] [Updated] (AMBARI-8220) Hadoop install with yum timesout after 10 mins

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

Alejandro Fernandez updated AMBARI-8220:
----------------------------------------
    Attachment: AMBARI-8220.patch

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