> Hi, thank's for answering. Yes I'm using clustering framwork and > membershipChangedDuringMerge, but I didn't find any correct > alghorithm > how to choose value for conflicting keys. (e.g. Timestamping) > > I hoped that I would find this idea in source code for > DistributedStateService but as I understand its and > JavaGroups behavior > after partition merge, DistributedStateService can be in inconsistent > state. (differend global state data on differend cluster > nodes) Am I right? > > I'm afraid that this problem is unsolvable and there allways be > situations in cluster, that after partition merge, cluster will be in > inconsistent state and would produce wrong output.
No. Cases: - DRM: we refresh total view after merging - Http session: sticky sessions => the last state is always correct - SFSB: we always use the same node and the last state will be resent to other node at merge time ------------------------------------------------------- This SF.net email is sponsored by: The Definitive IT and Networking Event. Be There! NetWorld+Interop Las Vegas 2003 -- Register today! http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
