infinispan usage
Paul Hethmon
paul.hethmon at clareitysecurity.com
Wed Sep 7 19:34:56 BST 2011
On 9/7/11 12:07 PM, "Chad La Joie" <lajoie at itumi.biz> wrote:
>Perhaps thats the issue. I've never used the multi-cast mechanism, I
>don't think. I've always used method where you expressing indicate
>which cluster nodes there are and have it do the health check via
>explicit pings.
Yea, I've had to learn a lot about multicast and there is more that I
don't know. But it looked like the UDP multicast was the recommended
network topology, though with a small cluster, it probably doesn't matter
a lot. The one nice thing about multicast, at least for my environment, is
that I don't have to explicitly make the configuration know about each
node. Maybe the TCP option can do the same, but I haven't looked at it
closely.
What I'm trying to achieve though is the easiest way to configure a
cluster. I'm running about 60 or 70 Shib clusters right now. Not all of
them are configured for session support and hence need clustering, but
enough of them. So I should be able to get away with only having to change
the port configuration for each cluster to keep them separate. I can tell
them to use 239.0.0.1 as the mcast_addr and then change ports. So cluster
1 gets port 10000, cluster 2 gets 10100, etc.
Next step is to figure out whether replication or distribution is the
better method. Well, actually next is to get replication working at all.
thanks,
Paul
More information about the dev
mailing list