Ok, how about:
* Provide a MergeHandler configuration
* Defaults to IgnoreOnMerge, which does nothing. FlushOnMerge also provided, which
flushes in-memory state on merge
* Allows users to write their own MergeHandlers, which are basically called when a
MergeView is received.
* Users could also do something similar in a CacheListener's viewChange() callback.
But more important than this, how can an instance tell if there has been a split, and it
is not in the primary partition *before* a merge takes place? E.g., in your example of
{A,B,C} and {D,E}, how can instance E decide to shutdown and not process requests?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4084399#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...