[ https://issues.jboss.org/browse/AS7-4512?page=com.atlassian.jira.plugin.s... ] Heiko Rupp updated AS7-4512: ---------------------------- Description: In previous versions of AS, the cluster partition name was exposed and user changeable. Users expect to set that in order to build different clusters. This should be exposed r/w in the management api. See also https://issues.jboss.org/browse/ISPN-1976 was: In previous versions of AS, the cluster partition name was exposed and user changeable. Users expect to set that in order to build different clusters. See also https://issues.jboss.org/browse/ISPN-1976 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-4512?page=com.atlassian.jira.plugin.s... ] Paul Ferraro resolved AS7-4512. ------------------------------- Resolution: Rejected 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) As Rado mentioned, you wouldn't want to isolate your clusters via cluster name alone - this would be done via distinct jgroups-udp multicast-address/port socket bindings. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-4512?page=com.atlassian.jira.plugin.s... ] Paul Ferraro commented on AS7-4512: ----------------------------------- 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. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-4512?page=com.atlassian.jira.plugin.s... ] Paul Ferraro commented on AS7-4512: ----------------------------------- The socket-binding name for the udp stack can be retrieved via: read-attribute --node=/subsystem=jgroups/stack=udp/transport=TRANSPORT socket-binding Using the default configuration, this returns: jgroups-udp The multicast address/port can then be retrieved via: read-attribute multicast-address --node=/socket-binding-group=standard-sockets/socket-binding=jgroups-udp read-attribute multicast-port --node=/socket-binding-group=standard-sockets/socket-binding=jgroups-udp -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira