September 2018 - infinispan-issues

[JBoss JIRA] (ISPN-9511) Expired event is not raised when modifying an expired entry

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-9511?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-9511: -------------------------------- Fix Version/s: 9.4.0.Final (was: 9.4.0.CR3) > Expired event is not raised when modifying an expired entry > ----------------------------------------------------------- > > Key: ISPN-9511 > URL: https://issues.jboss.org/browse/ISPN-9511 > Project: Infinispan > Issue Type: Bug > Components: Listeners > Affects Versions: 9.3.3.Final > Reporter: William Burns > Assignee: William Burns > Fix For: 9.4.0.Final > > > Due to the old way of implementing remove expired for lifespan, we didn't raise an expired event when writing to an entry. This was mostly to cause circular dependencies. But with the new remove expired max idle changes, this is now possible. > Without this change listeners can be in an inconsistent state, possibly, as the following could happen: > 1. Entry is created > 2. Listener is notified of creation > 3. Entry expires (no event yet) > 4. Entry is written to (created) > 5. Listener is notified of creation. > In this case there is no intermediate state where the listener thought there was no entry. This also becomes problematic if you are listening only for events that don't include create. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9484) Near cache invalidation should ignore created events and should not contain values

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-9484?page=com.atlassian.jira.plugin.... ] William Burns reassigned ISPN-9484: ----------------------------------- Assignee: William Burns (was: Tristan Tarrant) > Near cache invalidation should ignore created events and should not contain values > ----------------------------------------------------------------------------------- > > Key: ISPN-9484 > URL: https://issues.jboss.org/browse/ISPN-9484 > Project: Infinispan > Issue Type: Sub-task > Components: Hot Rod > Affects Versions: 9.4.0.CR1 > Reporter: Tristan Tarrant > Assignee: William Burns > Fix For: 9.4.0.CR3 > > > Near caches register a listener which sends back unnecessary events (created) as well as unnecessary data (values). We can create a filter/converter to remove both. The client should still work with older servers which don't have the filter. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6026) Segment-aware shared cache stores

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-6026?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-6026: -------------------------------- Fix Version/s: 9.4.0.Final > Segment-aware shared cache stores > --------------------------------- > > Key: ISPN-6026 > URL: https://issues.jboss.org/browse/ISPN-6026 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores > Reporter: Tristan Tarrant > Assignee: William Burns > Fix For: 9.4.0.CR3, 9.4.0.Final > > > Shared cache stores (e.g. JDBC) should be segment-aware so that they only load the keys they own. > Possible implementation: add a segment id column, so that the store can SELECT * FROM table WHERE segment_id = segment > Need to think about how to reconstruct segment ids. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9315) Local Cache Store Striping

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-9315?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-9315: -------------------------------- Fix Version/s: 9.4.0.Alpha1 (was: 9.4.0.CR3) > Local Cache Store Striping > -------------------------- > > Key: ISPN-9315 > URL: https://issues.jboss.org/browse/ISPN-9315 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Reporter: Tristan Tarrant > Assignee: William Burns > Fix For: 9.4.0.Alpha1, 9.4.0.Final > > > Local Cache Loaders/Stores should be able to store data in a shared persistent location by splitting up into segments -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9315) Local Cache Store Striping

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-9315?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-9315: -------------------------------- Fix Version/s: 9.4.0.Final (was: 9.4.0.Alpha1) > Local Cache Store Striping > -------------------------- > > Key: ISPN-9315 > URL: https://issues.jboss.org/browse/ISPN-9315 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Reporter: Tristan Tarrant > Assignee: William Burns > Fix For: 9.4.0.Alpha1, 9.4.0.Final > > > Local Cache Loaders/Stores should be able to store data in a shared persistent location by splitting up into segments -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8905) Segment-aware non-shared cache stores

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-8905?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-8905: -------------------------------- Fix Version/s: 9.4.0.Alpha1 (was: 9.4.0.CR3) > Segment-aware non-shared cache stores > ------------------------------------- > > Key: ISPN-8905 > URL: https://issues.jboss.org/browse/ISPN-8905 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores > Reporter: William Burns > Assignee: William Burns > Fix For: 9.4.0.Alpha1, 9.4.0.Final > > > Non shared stores should allow for segment based store separation. This might involve creating a store per segment. But this allows for superior iteration performance over a subset of segments. > Distributed stores benefit the most from this due to the fact that iteration is done at the segment level to help ensure that duplicate entries are not retrieved. It also would be beneficial for state transfer and other operations that operate only upon a given set of segments. > This could be advantageous even for REPL and LOCAL caches as there is then a very clear separation of stores to process in parallel for given operations. This would have to be verified with tests to see if this is worth it though. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8380) OffHeap doesn't expire entries on access

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-8380?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-8380: -------------------------------- Fix Version/s: 9.4.0.Final > OffHeap doesn't expire entries on access > ---------------------------------------- > > Key: ISPN-8380 > URL: https://issues.jboss.org/browse/ISPN-8380 > Project: Infinispan > Issue Type: Bug > Components: Expiration, Off Heap > Affects Versions: 9.1.1.Final > Reporter: William Burns > Assignee: William Burns > Fix For: 9.4.0.CR3, 9.4.0.Final > > > Off Heap currently does not expire entries when they are read through a get or other operations. Instead it only removes entries when the reaper is ran. We need to make sure to remove these entries on access to free memory sooner. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7168) Prevent user from configuring passivation with a shared store

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-7168?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-7168: -------------------------------- Fix Version/s: 9.4.0.Final (was: 9.4.0.CR1) > Prevent user from configuring passivation with a shared store > ------------------------------------------------------------- > > Key: ISPN-7168 > URL: https://issues.jboss.org/browse/ISPN-7168 > Project: Infinispan > Issue Type: Bug > Affects Versions: 8.2.4.Final > Reporter: William Burns > Assignee: William Burns > Fix For: 9.4.0.CR3, 9.4.0.Final > > > Passivation only makes sense with a non shared cache store. --The problem is that if an entry is passivated on a shared cache store only the first node will be able to activate the entry and subsequent nodes will always see null.-- > Looking closer the bigger issue is if an entry becomes passivated and then subsequently written to you will have a different value in the store as you would in memory. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8905) Segment-aware non-shared cache stores

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-8905?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-8905: -------------------------------- Fix Version/s: 9.4.0.Final (was: 9.4.0.Alpha1) > Segment-aware non-shared cache stores > ------------------------------------- > > Key: ISPN-8905 > URL: https://issues.jboss.org/browse/ISPN-8905 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores > Reporter: William Burns > Assignee: William Burns > Fix For: 9.4.0.CR3, 9.4.0.Final > > > Non shared stores should allow for segment based store separation. This might involve creating a store per segment. But this allows for superior iteration performance over a subset of segments. > Distributed stores benefit the most from this due to the fact that iteration is done at the segment level to help ensure that duplicate entries are not retrieved. It also would be beneficial for state transfer and other operations that operate only upon a given set of segments. > This could be advantageous even for REPL and LOCAL caches as there is then a very clear separation of stores to process in parallel for given operations. This would have to be verified with tests to see if this is worth it though. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9483) TEST_PING doesn't trigger merge after JGroups 4.0.13 upgrade

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-9483?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-9483: ------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > TEST_PING doesn't trigger merge after JGroups 4.0.13 upgrade > ------------------------------------------------------------ > > Key: ISPN-9483 > URL: https://issues.jboss.org/browse/ISPN-9483 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 9.4.0.CR1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Labels: testsuite_stability > Fix For: 9.4.0.CR3 > > > In JGroups 4.0.13.Final, {{MERGE3}} started using the {{ASYNC_DISCOVERY_EVENT}} to find other members. {{TEST_PING}} doesn't handle the event correctly, at least when trace logging is enabled, and the merge never happens. > {{Discovery}} should handle the new event automatically, but it only works if the discovery protocol actively sends out {{GET_MBRS_REQ}} messages and receives {{GET_MBRS_RSP}} messages from other members. {{TEST_PING}} doesn't receive any {{GET_MBRS_RSP}} messages, so {{Discovery.addResponse()}} is never called. > This causes failures in all the tests that split the cluster and heal it, but for some reason CI isn't reporting the failures: > {noformat} > [OK: 70, KO: 1, SKIP: 0] Test failed: org.infinispan.distribution.rehash.RehashAfterPartitionMergeTest.testCachePartition[DIST_SYNC] > java.lang.RuntimeException: Timed out before caches had changed views ([[RehashAfterPartitionMergeTest[DIST_SYNC]-NodeB-45390], [RehashAfterPartitionMergeTest[DIST_SYNC]-NodeD-46782]]) to contain 2 members > at org.infinispan.test.TestingUtil.blockUntilViewsChanged(TestingUtil.java:761) > at org.infinispan.test.TestingUtil.blockUntilViewsChanged(TestingUtil.java:743) > at org.infinispan.distribution.rehash.RehashAfterPartitionMergeTest.testCachePartition(RehashAfterPartitionMergeTest.java:67) > {noformat} > https://ci.infinispan.org/job/Infinispan/job/master/808/consoleFull -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues September 2018