[
https://issues.apache.org/jira/browse/AMBARI-15492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15204807#comment-15204807
]
Hadoop QA commented on AMBARI-15492:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12794532/AMBARI-15492.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/5955//console
This message is automatically generated.
> Status commands fail randomly
> -----------------------------
>
> Key: AMBARI-15492
> URL: https://issues.apache.org/jira/browse/AMBARI-15492
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.2.2
> Reporter: Myroslav Papirkovskyy
> Assignee: Myroslav Papirkovskyy
> Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15492.patch
>
>
> We experience random failures of status commands sometimes.
> As we treat any status command failure as "stopped"("installed") result, this
> causes component (or even service if component is master) to appear as
> stopped until next status command fixes status (1 minute interval).
> This tends to be completely random and appear once in 6-8 hours on average.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
