[
https://issues.apache.org/jira/browse/AMBARI-12002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14592132#comment-14592132
]
Christopher Jackson commented on AMBARI-12002:
----------------------------------------------
[~sumitmohanty] Yes that's what we've been doing for some time. However we are
testing the scenario in which a node is added to the cluster post installation
of our custom service. And the same issue arrises.
The workaround is to add the new node, the install fails since our client is
installed prior to the dependencies. We then make an API call to remove our
CUSTOM_SERVICE/CUSTOM_CLIENT, Reinstall all clients, reinstall non-client
failed components, then make an api call to add back our
CUSTOM_SERVICE/CUSTOM_CLIENT, make an additional api call to install our
CUSTOM_SERER/CUSTOM_CLIENT on the node. As you can see that's a kludge and
having the ability to order install would be very helpful.
> Support ordered component installs.
> ------------------------------------
>
> Key: AMBARI-12002
> URL: https://issues.apache.org/jira/browse/AMBARI-12002
> Project: Ambari
> Issue Type: Improvement
> Affects Versions: 2.0.0
> Environment: HDP2.2, RHEL6
> Reporter: Christopher Jackson
>
> When defining a custom service it may involve a component which needs to
> modify another component. As such the order in which components install
> becomes important. This could be achieved by looking at the list of
> dependencies for a given component. It should enforce that all components
> listed as dependencies with a scope of host are installed prior to the given
> component.
> Per Sumit Mohanty, 'Its easy to implement an install order as well -
> basically call the same helper method as done for START.'
> In my use case I have CUSTOM_SERVICE/CUSTOM_CLIENT that has a scope:host
> dependency on HDFS/HDFS_CLIENT and HBASE/HBASE_CLIENT, I would expect
> HDFS_CLIENT and HBASE_CLIENT to install before CUSTOM_CLIENT.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
