You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ambari.apache.org by "Erin A Boyd (JIRA)" <ji...@apache.org> on 2015/06/04 20:48:38 UTC

[jira] [Resolved] (AMBARI-5829) Services fail to start up when after timeout

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

Erin A Boyd resolved AMBARI-5829.
---------------------------------
       Resolution: Won't Fix
    Fix Version/s:     (was: 2.1.0)

> Services fail to start up when after timeout 
> ---------------------------------------------
>
>                 Key: AMBARI-5829
>                 URL: https://issues.apache.org/jira/browse/AMBARI-5829
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Erin A Boyd
>            Assignee: Scott Creeley
>
> Services fail to start up after timeout of resource manager an/or mapred service check takes too long.  Check needs to be improved to either increase timeout, or make timeout more intelligent (rather than just check 60 times in 1 minute and fail)
> This happens almost every time when Ambari is installed with GlusterFS as the storage layer.



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