In ELB, we can use the concept of a Hazelcast light member. The Hazelcast instances designated for the underlying managed groups (e.g. wso2.as.domain, wso2.esb.domain) can be light members. However, the issue is, this is specified using a System property. Excerpt from the Hazelcast documentation:
"7.3. LiteMember LiteMembers are members with no storage. If -Dhazelcast.lite.member=true JVM parameter is set, then the JVM will join the cluster as a 'lite member' which will not be a 'data partition' (no data on that node) but will have super fast access to the cluster just like any regular member does." The problem with the system property is, the ELB itself is a part of a cluster, and we will need to replicate stuff between ELB nodes. So, there is no way to specify only selected Hazelcast instances as light members. -- *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 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* * * *Lean . Enterprise . Middleware*
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
