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

Hadoop QA commented on AMBARI-11940:
------------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12739764/AMBARI-11940.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 
ambari-server.

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

This message is automatically generated.

> Automatic retry of commands should be limited to initial INSTALL and START 
> only
> -------------------------------------------------------------------------------
>
>                 Key: AMBARI-11940
>                 URL: https://issues.apache.org/jira/browse/AMBARI-11940
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.1.0
>            Reporter: Sumit Mohanty
>            Assignee: Sumit Mohanty
>            Priority: Critical
>             Fix For: 2.1.0
>
>         Attachments: AMBARI-11940.patch
>
>
> The automatic retry of the tasks at the agent should be limited to the 
> initial INSTALL and START commands only.
> Retry is only needed during the initial install using blueprints to get 
> around the lack of role command order enforcements. Beyond the initial 
> install/start automatic retry can actually be hinderance to debugging errors. 
> While it is possible to modify {{cluster-env}} to disable this capability, by 
> default disabling auto-retry post initial INSTALL/START makes more sense.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to