[
https://issues.apache.org/jira/browse/WHIRR-221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Alves updated WHIRR-221:
------------------------------
Attachment: WHIRR-221.patch
First iteration patch, still not tested (and not compiling because of BYON
action):
- added the concept of dependencies
- added a dependency analyzer that creates stages: each stage is a set of roles
to be executed across instancetemplates before the next stage can begin
- Moved non script specific stuff in ScriptBasedClusterAction to ClusterAction
including a generic stage execution system (each action sets a callable in the
ClusterActionEvent and this callable is executed by ClusterAction in a per
stage basis).
- All actions that inherited from ScriptBasedCluster action are now stage
oriented, the only one that is not is BoostrapClusterAction.
- Took the chance to remove the deprecated call of ScripBaseClusterAction
To Come:
- DryRunTests (ongoing)
- Perform the Itests
- Finish BYON (which should be stage aware)
> 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.7.1, 0.8.0
> Reporter: Andrei Savu
> Assignee: David Alves
> Priority: Critical
> Fix For: 0.8.0
>
> Attachments: WHIRR-221-v1.patch, WHIRR-221-v3.patch, WHIRR-221.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.
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
