[infinispan-issues] [JBoss JIRA] (ISPN-1342) Support for Near-Cache Pattern
Mikolaj Gierulski (JIRA)
issues at jboss.org
Tue Mar 11 12:09:11 EDT 2014
[ https://issues.jboss.org/browse/ISPN-1342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12952043#comment-12952043 ]
Mikolaj Gierulski commented on ISPN-1342:
-----------------------------------------
I think I was able to achieve this in a patched version of 6.0.0.Final.
I created a dist cache with L1 enabled and nearcache nodes having capacityFactor="0" configured (this required patching, as capacityFactor configuration doesn't work in 6.0.0.Final).
> Support for Near-Cache Pattern
> ------------------------------
>
> Key: ISPN-1342
> URL: https://issues.jboss.org/browse/ISPN-1342
> Project: Infinispan
> Issue Type: Feature Request
> Components: Core
> Affects Versions: 5.0.0.FINAL
> Reporter: Peter Novak
> Assignee: Manik Surtani
>
> Please create some support for near-cache pattern for distributed cache. Some detailed description could be found in Oracle Coherence documentation http://download.oracle.com/docs/cd/E13924_01/coh.340/e13819/nearcache.htm or in Cameron Purdy presentation http://frech.info/themen/CameronPurdy-DistributedCachingEssentialLessons.pdf
> It is based on combination of L1 caching in local JVM of application with combination of L2 cache based on distributed cache cluster on other servers. I tried to implement this myself, but HotRod does not support Client-side listeners (The UnsupportedOperationException is thrown). It could be cool, if I could register some kind of eviction listener on client side and use it for invalidation of records in local cache based on event from remote distributed cache (L2).
> Some kind of workaround was described in http://community.jboss.org/thread/166993 : "We don't have L1s yet, but you could implement Cache Listeners on the server side and use JMS to notify your clients and build an L1 that way."
> Thanks for so great cache like infinispan is.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the infinispan-issues
mailing list