ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Nettleton (JIRA)" <>
Subject [jira] [Updated] (AMBARI-11866) Blueprints processor should enable command retry by default
Date Thu, 11 Jun 2015 20:11:00 GMT


Robert Nettleton updated AMBARI-11866:
    Attachment: AMBARI-11866.patch

Uploaded initial version of patch.

> Blueprints processor should enable command retry by default
> -----------------------------------------------------------
>                 Key: AMBARI-11866
>                 URL:
>             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

View raw message