[
https://issues.apache.org/jira/browse/AMBARI-11940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14587382#comment-14587382
]
Sumit Mohanty commented on AMBARI-11940:
----------------------------------------
All relevant server side unit tests passed. Manually tested and verified that
retry is only used for the initial phase of cluster install and add host.
> 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)
