[jboss-jira] [JBoss JIRA] Commented: (JBCACHE-471) Handle JGroups MERGE
[ http://jira.jboss.com/jira/browse/JBCACHE-471?page=comments#action_12390431 ]
Manik Surtani commented on JBCACHE-471:
---------------------------------------
Decided to provide a policy based approach here. When we get a JGroups notification of a
merge, provide plugins that allow for:
1) Evict entire cluster state (useful with Hibernate)
2) Evict cache state of the losing sub-cluster
3) Throw exception, stop cache (useful if we need to force some manual cleanup)
4) Perform merging of disjointed subtrees. (Maybe later - this "plugin" could
be released in future)
Handle JGroups MERGE
--------------------
Key: JBCACHE-471
URL: http://jira.jboss.com/jira/browse/JBCACHE-471
Project: JBoss Cache
Issue Type: Task
Security Level: Public(Everyone can see)
Affects Versions: 1.2.4
Reporter: Manik Surtani
Assigned To: Manik Surtani
Fix For: 2.2.0.GA
When JGroups needs to do a merge due to a temporary break in the group structure, JGroups
does not handle the merging of data. This is usually left up to the application to
handle.
JBossCache should support pluggable merge policies, we could provide some simple merge
policies and allow users to write their own.
1. Evict on merge policy - when a merge occurs, evict the entire in-memory state.
Useful for Hibernate or when used with a shared cache loader.
2. Other merge algos ... ?
--
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira