[
https://issues.apache.org/jira/browse/AMBARI-15202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15170325#comment-15170325
]
Hadoop QA commented on AMBARI-15202:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12790178/AMBARI-15202.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{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:red}-1 core tests{color}. The patch failed these unit tests in
ambari-server:
org.apache.ambari.server.agent.HeartbeatProcessorTest
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/5600//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/5600//console
This message is automatically generated.
> Status commands temporary break host component state machine
> ------------------------------------------------------------
>
> Key: AMBARI-15202
> URL: https://issues.apache.org/jira/browse/AMBARI-15202
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 1.6.0
> Reporter: Myroslav Papirkovskyy
> Assignee: Myroslav Papirkovskyy
> Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15202.patch
>
>
> This occurs when status command response is received after start of next
> stage which modifies sch state (quite often on starting services during
> install).
> # status command is sent to agent (happens every 60 seconds)
> # start commands are scheduled, generated event which move sch from INSTALLED
> to STARTING
> # status command response received from agent. sch status directly set to
> INSTALLED bypassing state machine
> # All subsequent task reports from agent trigger InvalidTransitionException,
> as OP_INPROGRESS event tries to do STARTING -> STARTING transition.
> # However at task end we support INSTALLED -> STARTED transition for STARTED
> event. So tasks finish normally.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
