[
https://issues.apache.org/jira/browse/AMBARI-8189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14511371#comment-14511371
]
Dmitry Lysnichenko commented on AMBARI-8189:
--------------------------------------------
Through parallel installation might be disabled by default, patch causes
execution of commands like START/STOP to be done in a separate thread. That
means that STATUS commands now are executed in parallel with commands like
START/STOP, and sometimes break state machine with race conditions:
e.g. Component is STARTING, but before it reports being STARTED, STATUS command
is executed and host component state changes to INSTALLED (as there is no
running process yet). After that, server receives COMPLETED command report on
STARTING operation, but fails to perform (now invalid) transition
INSTALLED->STARTED.
> Ambari agent support for parallel task execution during deployment
> ------------------------------------------------------------------
>
> Key: AMBARI-8189
> URL: https://issues.apache.org/jira/browse/AMBARI-8189
> Project: Ambari
> Issue Type: Task
> Affects Versions: 2.0.0
> Reporter: Ivan Mitic
> Assignee: Ivan Mitic
> Fix For: 2.1.0
>
> Attachments: AMBARI-8189.2.patch, AMBARI-8189.patch
>
>
> Ambari serializes all operations on the node, and by actually parallelizing
> the independent setup activities, deployment time would significantly
> decrease. Ambari stack definition already defines a notion of service
> dependencies, so some basic infra requirements for parallel execution are
> already in place.
> This is a tracking Jira where we can discuss this proposal and work on the
> design/prototype and patch.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
