Hi Akila, It's the instances in a cluster that resides in one hazelcast domain not all the cartridge instances.
And in a multi-region deployment, we should use public IPs of members as well-known addresses. That's all we have to do. On Sat, May 24, 2014 at 8:52 PM, Akila Ravihansa Perera <[email protected]>wrote: > Hi, > > In Private PaaS we have different Apache Stratos clusters created for > each WSO2 service (for eg - AS, ESB, IS, APIM). If clustering is > enabled at the service deployment, each instance in the same cluster > will update its axis2.xml with well known members' IP addresses in > that cluster. Basically they are in the same Hazelcast domain. For now > we have only considered service deployments in a single network > partition on Stratos. > > Can someone explain how this should be handled when multiple network > partitions are deployed in Stratos? > > In multiple network partitions scenario, the same Stratos cluster will > span across different network partitions (perhaps in different > IaaS'es). Should we consider all instances (in different network > partitions) to be in the same Hazelcast domain? > > Thanks. > > -- > Akila Ravihansa Perera > Software Engineer > WSO2 Inc. > http://wso2.com > > Phone: +94 77 64 154 38 > Blog: http://ravihansa3000.blogspot.com > -- Thanks & regards, Nirmal Senior Software Engineer- Platform Technologies Team, WSO2 Inc. Mobile: +94715779733 Blog: http://nirmalfdo.blogspot.com/
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
