You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ambari.apache.org by "Sebastian Toader (JIRA)" <ji...@apache.org> on 2016/08/22 14:00:27 UTC

[jira] [Updated] (AMBARI-16217) Command execution by single python executor.

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

Sebastian Toader updated AMBARI-16217:
--------------------------------------
    Fix Version/s:     (was: 2.4.1)
                   2.5.0

> Command execution by single python executor.
> --------------------------------------------
>
>                 Key: AMBARI-16217
>                 URL: https://issues.apache.org/jira/browse/AMBARI-16217
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-server
>            Reporter: Sebastian Toader
>             Fix For: 2.5.0
>
>
> Currently, all commands are executed via own python executor - either serially or in parallel. Instead, a single python executor can be created to execute all commands. When all commands are combined, then one execution of before-install/start and after-install/start would suffice. In addition, all starts can be called in parallel while configure can be serialized where there are shared resources.



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