ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-15795) Parallel execution should only be allowed on commands that have auto retry enabled
Date Mon, 11 Apr 2016 15:57:25 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-15795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15235347#comment-15235347
] 

Hadoop QA commented on AMBARI-15795:
------------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12797958/AMBARI-15795.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:green}+1 core tests{color}.  The patch passed unit tests in .

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/6348//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/6348//console

This message is automatically generated.

> 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.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)

Mime
View raw message