[
https://issues.apache.org/jira/browse/AMBARI-15795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15239560#comment-15239560
]
Hudson commented on AMBARI-15795:
---------------------------------
SUCCESS: Integrated in Ambari-branch-2.2 #629 (See
[https://builds.apache.org/job/Ambari-branch-2.2/629/])
AMBARI-15795. Parallel execution should only be allowed on commands that
(smohanty:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=d8e0475808d6ab19ebcf032e582c7ef11a8b7593])
* ambari-agent/src/test/python/ambari_agent/TestActionQueue.py
* ambari-agent/src/main/python/ambari_agent/ActionQueue.py
> Parallel execution should only be allowed on commands that have auto retry
> enabled
> ----------------------------------------------------------------------------------
>
> Key: AMBARI-15795
> URL: https://issues.apache.org/jira/browse/AMBARI-15795
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
> Affects Versions: 2.2.2
> Reporter: Sumit Mohanty
> Assignee: Sumit Mohanty
> Fix For: 2.2.2
>
> Attachments: AMBARI-15795.2.patch, AMBARI-15795.patch
>
>
> Parallel execution of commands can result in failures if the commands process
> resources that are shared among the commands. For example, commands may check
> and delete the same file resource. Deleting a file resource that is already
> deleted is not a functional error but its does result in command failure.
> Its not always possible to guarantee that stack scripts are written with
> guards that can check the failure and then determine if its harmless or not.
> Auto retry is a way to get around failures due to resource contention - think
> eventual success. Try all commands in parallel - then try only the failed
> ones. Each command is idempotent by definition so after a few retries all
> commands succeed.
> When commands without auto-retry option are executed in parallel then there
> is no option to retry. This is not desirable.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
