[ http://jira.jboss.com/jira/browse/JBAS-1476?page=comments#action_12315505 ] Adrian Brock commented on JBAS-1476: ------------------------------------
We do need the GUID agreed across the cluster. This is what differentiates the particular instantiation of the cluster (similar to a java object instance). Rather than the Partition name, which identifies a logical group of servers that behaves as one server to the client (similar to a java class). The notion of partition name survives across restarts of the entire cluster and exists for all time in the client configuration. e.g. I want to use the JMSPartition Where the GUID only survives while there is a cluster in existance. This whole problem is really a corner case in that in principle the cluster should always be in existance. The only time this processing is required is: 1) Somebody reboots all nodes in a cluster, starting a new instance of the partition 2) Somebody moves the client to a different physical cluster with the same logical partition name. > Need to include a notion of cluster instance in the cluster view > ---------------------------------------------------------------- > > Key: JBAS-1476 > URL: http://jira.jboss.com/jira/browse/JBAS-1476 > Project: JBoss Application Server > Type: Bug > Components: Clustering > Versions: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final, JBossAS-4.0.1 SP1 > Reporter: Adrian Brock > Priority: Critical > > > We need to include a notion of cluster instance in the cluster view id > to avoid at least the following scenario: > Client serializes a handle to a cluster which is at cluster view 22 > Handle contains key DefaultPartition/HAJNDI/22 > The cluster is totally restarted meaning the view reverts back to one. > The client now has a view id > DefaultPartition/HAJNDI/1 > The client deserializes the handle, which will overwrite the correct cluster > view with the old invalid view. > ---- > This will also avoid the problem where a client talks to different clusters > with the same partition name. > ---- > Proposed solution: > 1) At cluster formation (first node in cluster), create a cluster instance > GUID > 2) At cluster join (second+ node in cluster) get the GUID from the coordinator > 3) Include this GUID in cluster view keys, i.e. > GUID/DefaultPartition/HAJNDI/1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
