ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alejandro Fernandez (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-9972) Provide means to skip INSTALL commands when bits are already installed on the node
Date Sat, 07 Mar 2015 00:52:39 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-9972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14351241#comment-14351241
] 

Alejandro Fernandez commented on AMBARI-9972:
---------------------------------------------

This is a good idea. For most/all components, the INSTALL command has to check the packages
(which is time consuming), and in cases where multiple versions exist, set which version of
the binaries to use (right now only done by hdp-select). I don't think we can skip sending
the command, but we can optimize its execution time on the agent.

> Provide means to skip INSTALL commands when bits are already installed on the node
> ----------------------------------------------------------------------------------
>
>                 Key: AMBARI-9972
>                 URL: https://issues.apache.org/jira/browse/AMBARI-9972
>             Project: Ambari
>          Issue Type: Task
>            Reporter: Ivan Mitic
>             Fix For: 2.0.0
>
>
> To better support cloud deployments, Ambari should be able to recognize that packages
have already been preinstalled on the VM image, and skip the INSTALL commands. Based on the
measurements with latest Ambari 2.0 and HDP 2.2, INSTALL phase takes ~3 minutes, so skipping
these steps will contribute significantly to the overall deployment latency.
> Things are not as strait forward as mentioned above, as some components might do some
steps beyond just INSTALL, but that's ok given that these are exceptions we can handle/eliminate
on case-by-case basis.
> Ambari preinstall and postinstall hooks can generally be run only once during sys-prep
so there shouldn't be any problems there. 
> Let's use this Jira to further discuss the design and come up with a patch that will
address this requirement. 



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

Mime
View raw message