Hi Azeez,
On Tue, Apr 1, 2014 at 5:17 PM, Afkham Azeez <[email protected]> wrote: > > No we don't create a separate Hazelcast cluster, we avoided this by >> creating our own group management functionality on top of Hazelcast, where >> in ntask component, a node can host specific types of tasks, and then >> later, through our API, we can list all the nodes that belongs to a >> specific task type (i.e. group name). >> > > So you are using the same HazelcastInstance that is provided by the > kernel; which means that the ELB member will also be seen as a member by > the task component. > Yep. Cheers, Anjana. > >> Cheers, >> Anjana. >> -- >> *Anjana Fernando* >> Technical Lead >> WSO2 Inc. | http://wso2.com >> lean . enterprise . middleware >> > > > > -- > *Afkham Azeez* > Director of Architecture; WSO2, Inc.; http://wso2.com > Member; Apache Software Foundation; http://www.apache.org/ > * <http://www.apache.org/>* > *email: **[email protected]* <[email protected]> > * cell: +94 77 3320919 <%2B94%2077%203320919> blog: * > *http://blog.afkham.org* <http://blog.afkham.org> > *twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> > * linked-in: **http://lk.linkedin.com/in/afkhamazeez > <http://lk.linkedin.com/in/afkhamazeez>* > > *Lean . Enterprise . Middleware* > -- *Anjana Fernando* Technical Lead WSO2 Inc. | http://wso2.com lean . enterprise . middleware
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
