[
https://issues.apache.org/jira/browse/WHIRR-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13199519#comment-13199519
]
David Alves commented on WHIRR-221:
-----------------------------------
turns our quite a lot has to change for this to happen.
for one clusteractionevents no longer have a one-to-one relationship to
instancetemplates. instead each template will have multiple ones, each one for
a single stage this can be seen in the execute() method. also the doAction()
method had to change signature.
Andrei:
I get that we need timeouts has some services's scripts will return success
before the service is actually running. How do you suggest we implement this?
my idea would be that each handler could return (optionally) a waitTime for the
service to be available, at each state, after all scripts were executed whirr
would wait for the longest of these times.
I mean if services have no need for a wait time then why wait.
Something else came to mind while implementing dependencies: default service
configuration and implicit roles. Let me clarify: if we start a hbase cluster
we need a zookeeper cluster, it would be nice if whirr could figure that out
and install zookeeper without the user explicitely telling it to. In this case
the zookeeper handler could return a typical layout for zookeeper depending on
cluster size (<3 nodes clusters 1 zk node, 3<=cluster<5 3 zk nodes cluster>=5 5
zk nodes. And this is a complex case, more often that not services can simply
be installed in all nodes.
have a look at:
https://github.com/dralves/whirr/blob/7227fb67a7b8623000df59fae3026713eb0f868f/core/src/main/java/org/apache/whirr/actions/ScriptBasedClusterAction.java
> 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
> 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
>
>
> 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
