[JBoss JIRA] (ISPN-10754) OffHeap code cleanup
by Will Burns (Jira)
Will Burns created ISPN-10754:
---------------------------------
Summary: OffHeap code cleanup
Key: ISPN-10754
URL: https://issues.jboss.org/browse/ISPN-10754
Project: Infinispan
Issue Type: Task
Components: Off Heap
Reporter: Will Burns
Assignee: Will Burns
Fix For: 10.0.0.Final
A few areas of off heap should be cleaned up that are remnants of old changes
# eviction old memory address can be deallocated outside of lrulock
# resizeIteration can be simplified by just updating bucket address (now that we only read one bucket at a time)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months
[JBoss JIRA] (ISPN-10667) Wrong count for size() if expiration and eviction is configured for <off-heap>
by Will Burns (Jira)
[ https://issues.jboss.org/browse/ISPN-10667?page=com.atlassian.jira.plugin... ]
Will Burns resolved ISPN-10667.
-------------------------------
Resolution: Rejected
We talked about this before, the issue with the count decreasing is because the expired entries were never removed and due to the access pattern LFU was retaining the expired entries and removing newer entries.
> Wrong count for size() if expiration and eviction is configured for <off-heap>
> ------------------------------------------------------------------------------
>
> Key: ISPN-10667
> URL: https://issues.jboss.org/browse/ISPN-10667
> Project: Infinispan
> Issue Type: Bug
> Reporter: Wolf-Dieter Fink
> Assignee: Will Burns
> Priority: Major
>
> If entries are added and eviction is enabled the client will stuck if the count is reached and fail after a bit with a SocketTimeout.
> The server will continue eviction until the number_of_entries is counted down to "0"
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months
[JBoss JIRA] (ISPN-10488) Infinispan Version is not printed in Quarkus native mode
by Katia Aresti (Jira)
[ https://issues.jboss.org/browse/ISPN-10488?page=com.atlassian.jira.plugin... ]
Katia Aresti updated ISPN-10488:
--------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Infinispan Version is not printed in Quarkus native mode
> --------------------------------------------------------
>
> Key: ISPN-10488
> URL: https://issues.jboss.org/browse/ISPN-10488
> Project: Infinispan
> Issue Type: Sub-task
> Components: Quarkus
> Affects Versions: 10.0.0.Beta5
> Reporter: Will Burns
> Assignee: Will Burns
> Priority: Major
> Fix For: 10.0.0.Final
>
>
> The client prints out the version of Infinispan at startup. Unfortunately for the client the VERSION String is computed at runtime on each invocation. Unfortunately in native mode we don't have the package implementation version available. Instead we should write this version to a static variable that is readable during native runtime. Note this is already handled for the server as it is written to a static variable.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months
[JBoss JIRA] (ISPN-10522) EvictionWithPassivationTest.testBasicStore random failures
by Will Burns (Jira)
[ https://issues.jboss.org/browse/ISPN-10522?page=com.atlassian.jira.plugin... ]
Will Burns resolved ISPN-10522.
-------------------------------
Resolution: Duplicate Issue
This was fixed in ISPN-10458
> EvictionWithPassivationTest.testBasicStore random failures
> ----------------------------------------------------------
>
> Key: ISPN-10522
> URL: https://issues.jboss.org/browse/ISPN-10522
> Project: Infinispan
> Issue Type: Bug
> Components: Core, Test Suite - Core
> Affects Versions: 10.0.0.CR1
> Reporter: Dan Berindei
> Assignee: Will Burns
> Priority: Major
> Labels: testsuite_stability
> Fix For: 10.0.0.Final
>
> Attachments: ISPN-10317_pendinglockmanager_20190827-0945_EvictionWithPassivationTest-infinispan-core.log.gz
>
>
> So far it has failed for me every time I debugged the test from the IDE (with trace logging enabled).
> {noformat}
> 09:55:48,837 ERROR (testng-Test:[]) [TestSuiteProgress] Test failed: org.infinispan.eviction.impl.EvictionWithPassivationTest.testBasicStore[OBJECT]
> java.lang.AssertionError: expected [null] but found [B6]
> at org.testng.Assert.fail(Assert.java:96) ~[testng-6.14.3.jar:?]
> at org.testng.Assert.failNotEquals(Assert.java:776) ~[testng-6.14.3.jar:?]
> at org.testng.Assert.assertEqualsImpl(Assert.java:132) ~[testng-6.14.3.jar:?]
> at org.testng.Assert.assertEquals(Assert.java:118) ~[testng-6.14.3.jar:?]
> at org.testng.Assert.assertEquals(Assert.java:453) ~[testng-6.14.3.jar:?]
> at org.testng.Assert.assertEquals(Assert.java:463) ~[testng-6.14.3.jar:?]
> at org.infinispan.eviction.impl.EvictionWithPassivationTest.testBasicStore(EvictionWithPassivationTest.java:115) ~[test-classes/:?]
> {noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months
[JBoss JIRA] (ISPN-10697) Expiration reaper should be able to handle a huge number of expired entries
by Will Burns (Jira)
[ https://issues.jboss.org/browse/ISPN-10697?page=com.atlassian.jira.plugin... ]
Will Burns resolved ISPN-10697.
-------------------------------
Resolution: Duplicate Issue
Fixed in ISPN-10678
> Expiration reaper should be able to handle a huge number of expired entries
> ---------------------------------------------------------------------------
>
> Key: ISPN-10697
> URL: https://issues.jboss.org/browse/ISPN-10697
> Project: Infinispan
> Issue Type: Enhancement
> Affects Versions: 10.0.0.CR2
> Reporter: Wolf-Dieter Fink
> Assignee: Will Burns
> Priority: Major
>
> A use case where a huge number of entries are added and expire in a short period the reaper is not able to handle that and will have increasing backlog which cause OOM error.
> The TRACE messages within the logfiles are
> TRACE [org.infinispan.expiration.impl.ClusterExpirationManager] (pool-9-thread-1) Purging data container of expired entries
> TRACE [org.infinispan.expiration.impl.ClusterExpirationManager] (pool-9-thread-1) Submitting expiration removal for key WrappedByteArray{...} which had lifespan of 480000
> ..... 1,900,000 more
> TRACE [org.infinispan.expiration.impl.ClusterExpirationManager] (pool-9-thread-1) Purging data container completed in 15.45 minutes
> As shown the reaper run for >15 minutes but the lifespan is set to 480sec==8min so there is a massive overlap and the reaper is not able to delete the entries fast enough from the cache
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months