November 2016 - infinispan-issues

[JBoss JIRA] (ISPN-7170) WriteSkewCheck version can be reset with an entry in store and not in memory

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-7170?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-7170: -------------------------------- Status: Open (was: New) > WriteSkewCheck version can be reset with an entry in store and not in memory > ---------------------------------------------------------------------------- > > Key: ISPN-7170 > URL: https://issues.jboss.org/browse/ISPN-7170 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 8.2.4.Final > Reporter: William Burns > Assignee: William Burns > > Write skew version is reset back to 1 when an entry is not in memory but can be found in the data store. This can cause various issues and when Total Order is used can even cause write skew errors from a single writer if different nodes evict different keys. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7170) WriteSkewCheck version can be reset with an entry in store and not in memory

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-7170?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-7170: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4578 > WriteSkewCheck version can be reset with an entry in store and not in memory > ---------------------------------------------------------------------------- > > Key: ISPN-7170 > URL: https://issues.jboss.org/browse/ISPN-7170 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 8.2.4.Final > Reporter: William Burns > Assignee: William Burns > > Write skew version is reset back to 1 when an entry is not in memory but can be found in the data store. This can cause various issues and when Total Order is used can even cause write skew errors from a single writer if different nodes evict different keys. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 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: -------------------------------- Status: Open (was: Pull Request Sent) Git Pull Request: (was: https://github.com/infinispan/infinispan/pull/4578) > 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 > > 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. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 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: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4578 > 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 > > 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. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 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: -------------------------------- Status: Open (was: New) > 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 > > 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. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7170) WriteSkewCheck version can be reset with an entry in store and not in memory

by William Burns (JIRA)

William Burns created ISPN-7170: ----------------------------------- Summary: WriteSkewCheck version can be reset with an entry in store and not in memory Key: ISPN-7170 URL: https://issues.jboss.org/browse/ISPN-7170 Project: Infinispan Issue Type: Bug Components: Core Affects Versions: 8.2.4.Final Reporter: William Burns Assignee: William Burns Write skew version is reset back to 1 when an entry is not in memory but can be found in the data store. This can cause various issues and when Total Order is used can even cause write skew errors from a single writer if different nodes evict different keys. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7166) WriteSkewConsistencyTest.testValidationOnlyInPrimaryOwner[DIST_SYNC] random failures

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-7166?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-7166: ------------------------------- Status: Open (was: New) > WriteSkewConsistencyTest.testValidationOnlyInPrimaryOwner[DIST_SYNC] random failures > ------------------------------------------------------------------------------------ > > Key: ISPN-7166 > URL: https://issues.jboss.org/browse/ISPN-7166 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 9.0.0.Alpha4 > Reporter: Dan Berindei > Assignee: Dan Berindei > Labels: testsuite_stability > Fix For: 9.0.0.Beta1 > > > The test requires a key to have a specific primary owner and backup owner, but because is uses the default {{SynchronizedConsistentHashFactory}}, sometimes there's no segment meeting that requirement. > {noformat} > 16:52:02,516 ERROR (testng-WriteSkewConsistencyTest[DIST_SYNC]:[]) [TestSuiteProgress] Test failed: org.infinispan.container.versioning.WriteSkewConsistencyTest.testValidationOnlyInPrimaryOwner[DIST_SYNC] > java.lang.IllegalStateException: Could not find any segment owned by Cache '___defaultcache'@WriteSkewConsistencyTest[DIST_SYNC]-NodeB-47455, [Cache '___defaultcache'@WriteSkewConsistencyTest[DIST_SYNC]-NodeA-21455], primary segments: [33, 2, 3, 5, 37, 6, 41, 10, 45, 15, 48, 18, 50, 25, 59, 29], backup segments: {Cache '___defaultcache'@WriteSkewConsistencyTest[DIST_SYNC]-NodeA-21455=[35, 8, 40, 12, 14, 52, 21, 53, 22, 24, 57, 58, 27, 31]} > at org.infinispan.distribution.MagicKey.<init>(MagicKey.java:85) ~[test-classes/:?] > at org.infinispan.distribution.MagicKey.<init>(MagicKey.java:136) ~[test-classes/:?] > at org.infinispan.container.versioning.WriteSkewConsistencyTest.testValidationOnlyInPrimaryOwner(WriteSkewConsistencyTest.java:58) ~[test-classes/:?] > {noformat} > The test should either use a fixed key and accept random owners, or use a {{ControlledConsistentHashFactory}} to pin the owners. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7166) WriteSkewConsistencyTest.testValidationOnlyInPrimaryOwner[DIST_SYNC] random failures

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-7166?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-7166: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4643 > WriteSkewConsistencyTest.testValidationOnlyInPrimaryOwner[DIST_SYNC] random failures > ------------------------------------------------------------------------------------ > > Key: ISPN-7166 > URL: https://issues.jboss.org/browse/ISPN-7166 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 9.0.0.Alpha4 > Reporter: Dan Berindei > Assignee: Dan Berindei > Labels: testsuite_stability > Fix For: 9.0.0.Beta1 > > > The test requires a key to have a specific primary owner and backup owner, but because is uses the default {{SynchronizedConsistentHashFactory}}, sometimes there's no segment meeting that requirement. > {noformat} > 16:52:02,516 ERROR (testng-WriteSkewConsistencyTest[DIST_SYNC]:[]) [TestSuiteProgress] Test failed: org.infinispan.container.versioning.WriteSkewConsistencyTest.testValidationOnlyInPrimaryOwner[DIST_SYNC] > java.lang.IllegalStateException: Could not find any segment owned by Cache '___defaultcache'@WriteSkewConsistencyTest[DIST_SYNC]-NodeB-47455, [Cache '___defaultcache'@WriteSkewConsistencyTest[DIST_SYNC]-NodeA-21455], primary segments: [33, 2, 3, 5, 37, 6, 41, 10, 45, 15, 48, 18, 50, 25, 59, 29], backup segments: {Cache '___defaultcache'@WriteSkewConsistencyTest[DIST_SYNC]-NodeA-21455=[35, 8, 40, 12, 14, 52, 21, 53, 22, 24, 57, 58, 27, 31]} > at org.infinispan.distribution.MagicKey.<init>(MagicKey.java:85) ~[test-classes/:?] > at org.infinispan.distribution.MagicKey.<init>(MagicKey.java:136) ~[test-classes/:?] > at org.infinispan.container.versioning.WriteSkewConsistencyTest.testValidationOnlyInPrimaryOwner(WriteSkewConsistencyTest.java:58) ~[test-classes/:?] > {noformat} > The test should either use a fixed key and accept random owners, or use a {{ControlledConsistentHashFactory}} to pin the owners. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7169) Add marker interface to determine if a store can be shared or not

by William Burns (JIRA)

William Burns created ISPN-7169: ----------------------------------- Summary: Add marker interface to determine if a store can be shared or not Key: ISPN-7169 URL: https://issues.jboss.org/browse/ISPN-7169 Project: Infinispan Issue Type: Enhancement Components: Loaders and Stores Reporter: William Burns We should add a new marker interface to tell if a store can be shared or not. Then at configuration time if a store was marked as shared by the user but doesn't have the interface we can throw an exception explaining you should only share supported stores. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

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

by William Burns (JIRA)

William Burns created ISPN-7168: ----------------------------------- Summary: 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 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. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues November 2016