[
https://issues.apache.org/jira/browse/AMBARI-15202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15178326#comment-15178326
]
Hudson commented on AMBARI-15202:
---------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit #4436 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/4436/])
AMBARI-15202. Status commands temporary break host component state
(mpapyrkovskyy:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=236beac472b77b0f5b098ff15a7ce9d6332e52ae])
*
ambari-server/src/test/java/org/apache/ambari/server/agent/HeartbeatProcessorTest.java
*
ambari-server/src/main/java/org/apache/ambari/server/agent/HeartbeatProcessor.java
> 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)
