(11:18:18 AM) rhusar: pilhuhn: afaik the partition name was a perf killer, receiving messages on physical layer that are not intended for that node is a waste of network bandwidth moreover you need to parse the message through all stacks and then just dump it..

The way to build clusters is to use different UDP multicast group/port.

Radoslav Husar
added a comment - 16/Apr/12 2:12 PM I should say yet here again, this is not a way to build clusters.
(11:18:18 AM) rhusar: pilhuhn: afaik the partition name was a perf killer, receiving messages on physical layer that are not intended for that node is a waste of network bandwidth moreover you need to parse the message through all stacks and then just dump it..
The way to build clusters is to use different UDP multicast group/port.

The cluster name of a cache container (analogous to partition name) is already exposed via the management API.
e.g.
/subsystem=infinispan/cache-container=cluster/transport=TRANSPORT:read-attribute(name=cluster)

Heiko Rupp
added a comment - 16/Apr/12 3:35 PM Paul, additional question
if the user uses jgroups over tcp, the mc-address does not exist for obvious reasons. What would be a surrogate?
the exposed ISPN attribute has a default of 'undefined'. Is the user ever required to set it?

1. In the TCP case, cluster communication is unicast only - so cluster "isolation" is less of an issue - since cluster membership is explicit, either defined statically or via a specific discovery method (e.g. S3_PING for EC2). Note that the default tcp stack uses multicast for discovery (i.e. MPING), so isolated clusters would still want to use distinct multicast address/ports, defined via the jgroups-mping socket binding.

2. If undefined, the "cluster" attribute defaults to the cache container name.

Paul Ferraro
added a comment - 16/Apr/12 4:44 PM 1. In the TCP case, cluster communication is unicast only - so cluster "isolation" is less of an issue - since cluster membership is explicit, either defined statically or via a specific discovery method (e.g. S3_PING for EC2). Note that the default tcp stack uses multicast for discovery (i.e. MPING), so isolated clusters would still want to use distinct multicast address/ports, defined via the jgroups-mping socket binding.
2. If undefined, the "cluster" attribute defaults to the cache container name.

Ian Springer
added a comment - 18/May/12 5:17 PM Hi Paul,
Can you give me the full path of the multicast-address/port attributes we should be using to determine a host controller's cluster?
Thanks,
Ian