[JBoss JIRA] (ISPN-10981) CacheWriterTest.shouldWriteThoughUsingPutAll_partialSuccess random failures
by Dan Berindei (Jira)
[ https://issues.redhat.com/browse/ISPN-10981?page=com.atlassian.jira.plugi... ]
Dan Berindei reopened ISPN-10981:
---------------------------------
The fix broke {{JCache.removeAll()}}.
> CacheWriterTest.shouldWriteThoughUsingPutAll_partialSuccess random failures
> ---------------------------------------------------------------------------
>
> Key: ISPN-10981
> URL: https://issues.redhat.com/browse/ISPN-10981
> Project: Infinispan
> Issue Type: Bug
> Components: JCache
> Affects Versions: 10.1.0.Beta1
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Labels: testsuite_stability
> Fix For: 10.1.1.Final
>
>
> {{CacheWriterTest.shouldWriteThoughUsingPutAll_partialSuccess}} fails very often.
> {noformat}
> 17:34:36,699 ERROR [TestSuiteProgress] Test failed: CacheWriterTest.shouldWriteThroughRemoveAllSpecific_partialSuccess
> java.lang.AssertionError: expected:<Hola World> but was:<null>
> at org.junit.Assert.fail(Assert.java:88) ~[junit-4.12.jar:4.12]
> at org.junit.Assert.failNotEquals(Assert.java:834) ~[junit-4.12.jar:4.12]
> at org.junit.Assert.assertEquals(Assert.java:118) ~[junit-4.12.jar:4.12]
> at org.junit.Assert.assertEquals(Assert.java:144) ~[junit-4.12.jar:4.12]
> at org.jsr107.tck.integration.CacheWriterTest.shouldWriteThroughRemoveAllSpecific_partialSuccess(CacheWriterTest.java:1047) ~[cache-tests-1.1.0-tests.jar:?]
> {noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (ISPN-11020) Clustered Max Idle Take 2
by Will Burns (Jira)
[ https://issues.redhat.com/browse/ISPN-11020?page=com.atlassian.jira.plugi... ]
Will Burns updated ISPN-11020:
------------------------------
Fix Version/s: 11.0.0.Final
> Clustered Max Idle Take 2
> -------------------------
>
> Key: ISPN-11020
> URL: https://issues.redhat.com/browse/ISPN-11020
> Project: Infinispan
> Issue Type: Feature Request
> Components: Core, Expiration
> Reporter: Will Burns
> Assignee: Will Burns
> Priority: Major
> Fix For: 11.0.0.Final
>
>
> ISPN-9003 added in clustered max idle expiration. However the approach implemented can cause entries to entries to expire prematurely when a node is lost (due to only the primary having the latest access time). This was deemed not acceptable.
> The new approach will add a new touch command that is fired on an entry access of a max idle entry. This will slow down accesses as they will essentially be light weight synchronous writes, but should guarantee data is properly expired.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (ISPN-11020) Clustered Max Idle Take 2
by Will Burns (Jira)
[ https://issues.redhat.com/browse/ISPN-11020?page=com.atlassian.jira.plugi... ]
Will Burns updated ISPN-11020:
------------------------------
Status: Pull Request Sent (was: Coding In Progress)
Git Pull Request: https://github.com/infinispan/infinispan/pull/7722
> Clustered Max Idle Take 2
> -------------------------
>
> Key: ISPN-11020
> URL: https://issues.redhat.com/browse/ISPN-11020
> Project: Infinispan
> Issue Type: Feature Request
> Components: Core, Expiration
> Reporter: Will Burns
> Assignee: Will Burns
> Priority: Major
> Fix For: 11.0.0.Final
>
>
> ISPN-9003 added in clustered max idle expiration. However the approach implemented can cause entries to entries to expire prematurely when a node is lost (due to only the primary having the latest access time). This was deemed not acceptable.
> The new approach will add a new touch command that is fired on an entry access of a max idle entry. This will slow down accesses as they will essentially be light weight synchronous writes, but should guarantee data is properly expired.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months