[
https://issues.apache.org/jira/browse/WHIRR-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13203790#comment-13203790
]
David Alves commented on WHIRR-221:
-----------------------------------
thanks Ioannis
This procedure should be documented somewhere since from now on no dependency
can be added to whirr without going trough it (or letting the build fail).
Maybe a note on the wiki?
> 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.8.0
> Reporter: Andrei Savu
> Assignee: David Alves
> Priority: Critical
> Fix For: 0.8.0
>
> Attachments: WHIRR-221-karaf-feature-supplement_txt.patch,
> WHIRR-221-v1.patch, WHIRR-221-v3.patch, WHIRR-221.patch, WHIRR-221.patch,
> WHIRR-221.patch, WHIRR-221.patch, WHIRR-221.patch, error-karaf.txt
>
>
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
