[JBoss JIRA] (ISPN-4810) Local Transactional Cache loses data when eviction is enabled and there are multiple readers and one writer
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-4810?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-4810:
----------------------------------
Summary: Local Transactional Cache loses data when eviction is enabled and there are multiple readers and one writer (was: Local Transactional Cache looses data when eviction is enabled and there are multiple readers and one writer)
> Local Transactional Cache loses data when eviction is enabled and there are multiple readers and one writer
> -----------------------------------------------------------------------------------------------------------
>
> Key: ISPN-4810
> URL: https://issues.jboss.org/browse/ISPN-4810
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 6.0.2.Final
> Environment: Windows 7 x64 (NTFS)
> Oracle JDK1.7.0_40
> Apache Maven 3.0.5
> Reporter: Horia Chiorean
> Labels: modeshape
> Attachments: ispn_concurrent.zip
>
>
> Using Infinispan 6.0.2 and a local, transactional cache backed by a <singleFile> store, with eviction enabled and a small {{max-entries}} setting, we have the following scenario:
> * the main thread (i.e. the "writer") starts a transaction, adds a batch of strings into the cache and also appends the same strings into a List cache entry and then commits the transaction
> * after the above has finished (i.e. after tx.commit) it fires a number of reader threads where each reader thread
> ** checks that the string entries were added into the cache and
> ** checks that the entries were correctly appended to the List entry
> * the above steps are repeated a number of times
> On any given run, based on timing, we're seeing that at some point (after some time) some of the reader threads will not see the latest version of the List entry (i.e. will not see the latest elements that were added into the list) but rather an old, stale List (sort of a "lost update" scenario).
> If we either:
> * disable eviction or
> * set the {{max-entries}} to a large enough value (which I suspect has the same effect - not evicting anything) the problem doesn't show up.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 5 months
[JBoss JIRA] (ISPN-4810) Local Transactional Cache looses data when eviction is enabled and there are multiple readers and one writer
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-4810?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-4810:
----------------------------------
Labels: modeshape (was: )
> Local Transactional Cache looses data when eviction is enabled and there are multiple readers and one writer
> ------------------------------------------------------------------------------------------------------------
>
> Key: ISPN-4810
> URL: https://issues.jboss.org/browse/ISPN-4810
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 6.0.2.Final
> Environment: Windows 7 x64 (NTFS)
> Oracle JDK1.7.0_40
> Apache Maven 3.0.5
> Reporter: Horia Chiorean
> Labels: modeshape
> Attachments: ispn_concurrent.zip
>
>
> Using Infinispan 6.0.2 and a local, transactional cache backed by a <singleFile> store, with eviction enabled and a small {{max-entries}} setting, we have the following scenario:
> * the main thread (i.e. the "writer") starts a transaction, adds a batch of strings into the cache and also appends the same strings into a List cache entry and then commits the transaction
> * after the above has finished (i.e. after tx.commit) it fires a number of reader threads where each reader thread
> ** checks that the string entries were added into the cache and
> ** checks that the entries were correctly appended to the List entry
> * the above steps are repeated a number of times
> On any given run, based on timing, we're seeing that at some point (after some time) some of the reader threads will not see the latest version of the List entry (i.e. will not see the latest elements that were added into the list) but rather an old, stale List (sort of a "lost update" scenario).
> If we either:
> * disable eviction or
> * set the {{max-entries}} to a large enough value (which I suspect has the same effect - not evicting anything) the problem doesn't show up.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 5 months
[JBoss JIRA] (ISPN-4810) Local Transactional Cache looses data when eviction is enabled and there are multiple readers and one writer
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-4810?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-4810:
----------------------------------
Assignee: (was: Mircea Markus)
> Local Transactional Cache looses data when eviction is enabled and there are multiple readers and one writer
> ------------------------------------------------------------------------------------------------------------
>
> Key: ISPN-4810
> URL: https://issues.jboss.org/browse/ISPN-4810
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 6.0.2.Final
> Environment: Windows 7 x64 (NTFS)
> Oracle JDK1.7.0_40
> Apache Maven 3.0.5
> Reporter: Horia Chiorean
> Attachments: ispn_concurrent.zip
>
>
> Using Infinispan 6.0.2 and a local, transactional cache backed by a <singleFile> store, with eviction enabled and a small {{max-entries}} setting, we have the following scenario:
> * the main thread (i.e. the "writer") starts a transaction, adds a batch of strings into the cache and also appends the same strings into a List cache entry and then commits the transaction
> * after the above has finished (i.e. after tx.commit) it fires a number of reader threads where each reader thread
> ** checks that the string entries were added into the cache and
> ** checks that the entries were correctly appended to the List entry
> * the above steps are repeated a number of times
> On any given run, based on timing, we're seeing that at some point (after some time) some of the reader threads will not see the latest version of the List entry (i.e. will not see the latest elements that were added into the list) but rather an old, stale List (sort of a "lost update" scenario).
> If we either:
> * disable eviction or
> * set the {{max-entries}} to a large enough value (which I suspect has the same effect - not evicting anything) the problem doesn't show up.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 5 months
[JBoss JIRA] (ISPN-4919) Configuration templates
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-4919?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-4919:
----------------------------------
Status: Open (was: New)
> Configuration templates
> -----------------------
>
> Key: ISPN-4919
> URL: https://issues.jboss.org/browse/ISPN-4919
> Project: Infinispan
> Issue Type: Feature Request
> Components: Configuration
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Fix For: 7.1.0.Alpha1
>
>
> Currently there is a 1:1 relationship between configuration and named caches. While the programmatic API does have the ability to .read() an existing configuration to create a new one, the declarative config does not.
> We should introduce the concept of configuration inheritance, e.g.:
> {code}
> <local-cache name="eviction-cache">
> <eviction strategy="LIRS" maxEntries="10000"/>
> </local-cache>
> <local-cache name="mycache" template="eviction-cache" />
> {code}
> Possibly, cache templates should be made "abstract" so that they cannot be instantiated as named caches directly, e.g.:
> {code}
> <local-cache name="eviction-cache" abstract="true">
> ...
> </local-cache>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 5 months
[JBoss JIRA] (ISPN-1342) Support for Near-Cache Pattern
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-1342?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño commented on ISPN-1342:
----------------------------------------
With remote events implemented, it's now the time to address the near cache use case.
The simplest thing is to implement the near cache as part of the Java Hot Rod client. Doing so requires creating a remote event listener that listens for cache entry created, modified and removed events. On top of that, a converter needs to be created that builds a custom event containing the value for created and modified events. This converter class would need sharing between the client and the server, which is slightly problematic since the only module in common is commons, and it lacks the Converter interface, plus it would not make a lot of sense for the Converter to be present there. So, it makes sense to implement ISPN-4757 to enable callbacks to work with raw data.
> 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: Galder Zamarreño
> Fix For: 7.1.0.Final
>
>
> 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 was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 5 months
[JBoss JIRA] (ISPN-4919) Configuration templates
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-4919?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant commented on ISPN-4919:
---------------------------------------
Sure, [~rvansa], and I am also going to add <xs:unique> constraints to make sure there are no duplicate id declarations
> Configuration templates
> -----------------------
>
> Key: ISPN-4919
> URL: https://issues.jboss.org/browse/ISPN-4919
> Project: Infinispan
> Issue Type: Feature Request
> Components: Configuration
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Fix For: 7.1.0.Alpha1
>
>
> Currently there is a 1:1 relationship between configuration and named caches. While the programmatic API does have the ability to .read() an existing configuration to create a new one, the declarative config does not.
> We should introduce the concept of configuration inheritance, e.g.:
> {code}
> <local-cache name="eviction-cache">
> <eviction strategy="LIRS" maxEntries="10000"/>
> </local-cache>
> <local-cache name="mycache" template="eviction-cache" />
> {code}
> Possibly, cache templates should be made "abstract" so that they cannot be instantiated as named caches directly, e.g.:
> {code}
> <local-cache name="eviction-cache" abstract="true">
> ...
> </local-cache>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 5 months
[JBoss JIRA] (ISPN-4970) AvailabilityException and AvailabilityMode are in the wrong package
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-4970?page=com.atlassian.jira.plugin.... ]
Dan Berindei updated ISPN-4970:
-------------------------------
Status: Open (was: New)
> AvailabilityException and AvailabilityMode are in the wrong package
> -------------------------------------------------------------------
>
> Key: ISPN-4970
> URL: https://issues.jboss.org/browse/ISPN-4970
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 7.0.0.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Critical
> Fix For: 7.0.1.Final, 7.1.0.Final
>
>
> {{AvailabilityException}} and {{AvailabilityMode}} are in package {{org.infinispan.partionhandling}}, instead of {{org.infinispan.par*ti*tionhandling}}.
> For {{AvailabilityException}}, we could create a new exception in the proper package and make the old one extend the new one, but I'm not sure how we should handle {{AvailabilityMode}}.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 5 months
[JBoss JIRA] (ISPN-4939) The text is repeated three times in META-INF\services
by ratking (JIRA)
[ https://issues.jboss.org/browse/ISPN-4939?page=com.atlassian.jira.plugin.... ]
ratking updated ISPN-4939:
--------------------------
Description:
Download infinispan-7.0.0.Final-all.zip from http://infinispan.org/download/ and unzip the file.
{quote}
infinispan-embedded-7.0.0.Final.jar\META-INF\beans.xml
infinispan-embedded-7.0.0.Final.jar\META-INF\services\
infinispan-embedded-query-7.0.0.Final.jar\META-INF\services\
infinispan-remote-7.0.0.Final.jar\META-INF\services\
{quote}
Open these files with a text editor, you will find that the text is *repeated three times*.
disastrous
was:
Download infinispan-7.0.0.Final-all.zip from http://infinispan.org/download/ and unzip the file.
{quote}
infinispan-embedded-7.0.0.Final.jar\META-INF\beans.xml
infinispan-embedded-7.0.0.Final.jar\META-INF\services\*.*
infinispan-embedded-query-7.0.0.Final.jar\META-INF\services\*.*
infinispan-remote-7.0.0.Final.jar\META-INF\services\*.*
{quote}
Open these files with a text editor, you will find that the text is *repeated three times*.
> The text is repeated three times in META-INF\services
> -----------------------------------------------------
>
> Key: ISPN-4939
> URL: https://issues.jboss.org/browse/ISPN-4939
> Project: Infinispan
> Issue Type: Bug
> Components: Build process
> Affects Versions: 7.0.0.Final
> Reporter: ratking
> Priority: Blocker
>
> Download infinispan-7.0.0.Final-all.zip from http://infinispan.org/download/ and unzip the file.
> {quote}
> infinispan-embedded-7.0.0.Final.jar\META-INF\beans.xml
> infinispan-embedded-7.0.0.Final.jar\META-INF\services\
> infinispan-embedded-query-7.0.0.Final.jar\META-INF\services\
> infinispan-remote-7.0.0.Final.jar\META-INF\services\
> {quote}
> Open these files with a text editor, you will find that the text is *repeated three times*.
> disastrous
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 5 months
[JBoss JIRA] (ISPN-4939) The text is repeated three times in META-INF\services
by ratking (JIRA)
[ https://issues.jboss.org/browse/ISPN-4939?page=com.atlassian.jira.plugin.... ]
ratking updated ISPN-4939:
--------------------------
Description:
Download infinispan-7.0.0.Final-all.zip from http://infinispan.org/download/ and unzip the file.
{quote}
infinispan-embedded-7.0.0.Final.jar\META-INF\beans.xml
infinispan-embedded-7.0.0.Final.jar\META-INF\services\*.*
infinispan-embedded-query-7.0.0.Final.jar\META-INF\services\*.*
infinispan-remote-7.0.0.Final.jar\META-INF\services\*.*
{quote}
Open these files with a text editor, you will find that the text is *repeated three times*.
was:
Download infinispan-7.0.0.Final-all.zip from http://infinispan.org/download/ and unzip the file.
infinispan-embedded-7.0.0.Final.jar\META-INF\beans.xml
infinispan-embedded-7.0.0.Final.jar\META-INF\services\*.*
infinispan-embedded-query-7.0.0.Final.jar\META-INF\services\*.*
infinispan-remote-7.0.0.Final.jar\META-INF\services\*.*
Open these files with a text editor, you will find that the text is repeated three times.
> The text is repeated three times in META-INF\services
> -----------------------------------------------------
>
> Key: ISPN-4939
> URL: https://issues.jboss.org/browse/ISPN-4939
> Project: Infinispan
> Issue Type: Bug
> Components: Build process
> Affects Versions: 7.0.0.Final
> Reporter: ratking
> Priority: Blocker
>
> Download infinispan-7.0.0.Final-all.zip from http://infinispan.org/download/ and unzip the file.
> {quote}
> infinispan-embedded-7.0.0.Final.jar\META-INF\beans.xml
> infinispan-embedded-7.0.0.Final.jar\META-INF\services\*.*
> infinispan-embedded-query-7.0.0.Final.jar\META-INF\services\*.*
> infinispan-remote-7.0.0.Final.jar\META-INF\services\*.*
> {quote}
> Open these files with a text editor, you will find that the text is *repeated three times*.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 5 months