[ 
https://issues.apache.org/jira/browse/AMBARI-18553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sandor Magyari updated AMBARI-18553:
------------------------------------
    Attachment: AMBARI-18553_v4.patch

> Provision actions to happen based only on specified dependencies
> ----------------------------------------------------------------
>
>                 Key: AMBARI-18553
>                 URL: https://issues.apache.org/jira/browse/AMBARI-18553
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-server
>            Reporter: Sandor Magyari
>            Assignee: Sandor Magyari
>             Fix For: 2.5.0
>
>         Attachments: AMBARI-18553.patch, AMBARI-18553_v2.patch, 
> AMBARI-18553_v3.patch, AMBARI-18553_v4.patch
>
>
> Today, the START commands stored in role_command_orders table are bound to 
> multiple stages created based on dependencies between components - a 
> component in the second stage can only begin its START after the entire first 
> stage is done as opposed to just its dependencies in the first stage. This 
> eventually increases the overall blueprint deployment time.
> This Jira tracks STARTing components just based on dependency order as 
> specified by the role_command_order as opposed to the current stage based 
> model.
> The goal is to be able to configure a direct dependency based execution model 
> of commands, for now only for Blueprint based deployment commands.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to