Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Sat, 8 Nov 2014 00:41:33 +0000 (UTC)
From: "Hadoop QA (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12753853.1415402745000.450869.1415407293630@Atlassian.JIRA>
In-Reply-To: <JIRA.12753853.1415402745000@Atlassian.JIRA>
References: <JIRA.12753853.1415402745000@Atlassian.JIRA>
 <JIRA.12753853.1415402745264@arcas>
Subject: [jira] [Commented] (AMBARI-8220) Hadoop install with yum timesout
 after 10 mins
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Hadoop QA commented on AMBARI-8220:
-----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12680307/AMBARI-8220.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in ambari-server.

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/557//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/557//console

This message is automatically generated.

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