[
https://issues.apache.org/jira/browse/AMBARI-11940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14588453#comment-14588453
]
Hudson commented on AMBARI-11940:
---------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #2937 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/2937/])
AMBARI-11940. Automatic retry of commands should be limited to initial INSTALL
and START only (smohanty) (smohanty:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=222b0292e4e22db1e2be6bd03764280b3cbce837)
*
ambari-server/src/test/java/org/apache/ambari/server/controller/AmbariManagementControllerTest.java
*
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/HostComponentResourceProvider.java
*
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java
> 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)
