ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <>
Subject [jira] [Commented] (AMBARI-8220) Hadoop install with yum timesout after 10 mins
Date Sat, 08 Nov 2014 00:41:33 GMT


Hadoop QA commented on AMBARI-8220:

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment
  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
                        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:
Console output:

This message is automatically generated.

> Hadoop install with yum timesout after 10 mins
> ----------------------------------------------
>                 Key: AMBARI-8220
>                 URL:
>             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 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

View raw message