You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2015/06/12 01:56:02 UTC
[jira] [Commented] (AMBARI-11866) Blueprints processor should
enable command retry by default
[ https://issues.apache.org/jira/browse/AMBARI-11866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14582705#comment-14582705 ]
Hudson commented on AMBARI-11866:
---------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #2891 (See [https://builds.apache.org/job/Ambari-trunk-Commit/2891/])
AMBARI-11866. Blueprints processor should enable command retry by default. (rnettleton) (rnettleton: http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=dc25acbc953d0c6895e7fd6fee69618108fcbb8d)
* ambari-server/src/main/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessor.java
* ambari-server/src/test/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessorTest.java
> Blueprints processor should enable command retry by default
> -----------------------------------------------------------
>
> Key: AMBARI-11866
> URL: https://issues.apache.org/jira/browse/AMBARI-11866
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.1.0
> Reporter: Robert Nettleton
> Assignee: Robert Nettleton
> Priority: Critical
> Fix For: 2.1.0
>
> Attachments: AMBARI-11866.patch
>
> Original Estimate: 3h
> Remaining Estimate: 3h
>
> The new provisioning model used by Blueprints installs and starts services using much more parallelization. This means that some ordering issues not handled by individual components can occur, keeping some services from starting properly initially.
> The new command retry feature enabled in Ambari can be used to request that installs and commands be retried in the event of a failure.
> The details of the new retry feature can be found in AMBARI-11804.
> The Blueprint processor should enable this feature by default for Cluster deployments based on Blueprints. While providing valid defaults, the user should also be able to override these defaults in the "cluster-env" configuration section of either the Blueprint or Cluster Creation Template.
> I'm working on a fix for this, and will be submitting a patch shortly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)