[ http://jira.jboss.com/jira/browse/JBAS-1476?page=comments#action_12315503 ] Adrian Brock commented on JBAS-1476: ------------------------------------
I think the merge problem can be easily resolved by changes in the cluster family processing at the invoker client. e.g. Client is talking to HAJNDI GUID1/HAJNDI/4 (instance, service, view) It passes this info on the request and gets back a new view because the cluster has merged with another cluster that has decided it will contain the co-ordinator. GUID2/HAJNDI/3 So not only do we update the view, we also change the key from GUID1 to GUID2 to reflect the merge. i.e. The GUID1 views are now invalid and it will use the GUID2 views from now on. We can even add processing to the family where if a different proxy asks for the GUID1 view, it actually gets back the more up-to-date GUID2 view. > 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
