Re: [jboss-as7-dev] Clustered invocation design

mabe just keeping it simple. Each Node in cluster replicated state to exactly one other node in cluster, just everything which is defined as statefull. to which node might be load balanced. So on faile over you have exact copy of the same state on other node. So it doesn't mother which combinations... Am 21.11.2011 um 21:40 schrieb Scott Marlow: >> >> Summary >> ------- >> >> For both options, we have to determine an appropriate load-balancing >> strategy. The choice of direction will affect how our clustering and >> transaction interceptors function. We also have to suss out the logic >> around dealing with conflicting or wrongly-ordered topology updates; >> hopefully our existing policies will continue to apply. >> > > I just wanted to mention, that when we talk about load-balancing > strategies/policies, that we might need some strategies that can handle > affinity for groups derived from extended persistence. In other words, > this would be a policy that understands how to migrate a group of > stateful session beans to the same target node, during fail-over. > > > Another example, would be the same as above, except SFSB2 has a > reference to SFSB3, which has a different XPC3. XPC3 is also used by > SFSB4. So, the load balancing policy would be need to have some > heuristic or maybe group-id that covers this case. > > One reason for ensuring that the same node is chosen for groups derived > from use of extended persistence context, is so that applications can > continue to see dirty data that is associated with the XPC. > > _______________________________________________ > jboss-as7-dev mailing list > jboss-as7-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-as7-dev