[
https://issues.apache.org/jira/browse/WHIRR-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12992772#comment-12992772
]
Tom White commented on WHIRR-221:
---------------------------------
Thanks for the contribution David. This is great work, but I'm struggling to
see the use case that motivates the feature. It came up in the context of
HBase, but HBase works without it (as far as I know). I'm hesitant to add this
code without having at least one service that uses it. Lars/Andrei, perhaps you
can shed some more light? Thanks.
> Optionally control the order of starting services
> -------------------------------------------------
>
> Key: WHIRR-221
> URL: https://issues.apache.org/jira/browse/WHIRR-221
> Project: Whirr
> Issue Type: New Feature
> Components: core, documentation
> Affects Versions: 0.4.0
> Reporter: Andrei Savu
> Priority: Critical
> Fix For: 0.4.0
>
> Attachments: WHIRR-221-v1.patch, WHIRR-221.patch
>
>
> As Lars sugested in WHIRR-170:
> The user should "be able to optionally control the order (services start).
> This could be role based and specified like so
> {code}
> whirr.role-order=zk,nn+jt,dn+tt,hbase-master,hbase-regionserver
> {code}
> If not specified the system should make any effort to start the services as
> quickly as possible, for example in multiple threads. In other words, when
> the role-order is not given no guarantee about order can be given."
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
