[
https://issues.apache.org/jira/browse/AMBARI-17443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15350358#comment-15350358
]
Hadoop QA commented on AMBARI-17443:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12813563/AMBARI-17443.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/7548//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7548//console
This message is automatically generated.
> Allow commands to specify if they should be auto-retried upon failure
> ---------------------------------------------------------------------
>
> Key: AMBARI-17443
> URL: https://issues.apache.org/jira/browse/AMBARI-17443
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.4.0
> Reporter: Sumit Mohanty
> Assignee: Sumit Mohanty
> Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17443.patch
>
>
> During cluster creation using a blueprint, the initial INSTALL and START
> commands are automatically retried by the agent upon failure. This support
> was added to allow immediate scheduling of commands (as soon as hosts join
> the cluster) rather than waiting for all hosts to join.
> The feature itself is straight forward - if any command failed then agent
> will automatically retry them for a configurable duration.
> Auto retry itself is useful for other commands where user may want some
> retries before giving up - e.g. Restart commands. Rather than failing
> immediately agents can try a few more times. Its particularly useful if the
> start of a service depends on another service which is also being restarted.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
