March 2018 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-8786) Inconsistency if the WriteCommand isn't successful (triangle)

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-8786?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-8786: ------------------------------ Description: A stale read can happen in a backup owner if it performs a (conditional) write follow by a read operation. If the write operation fails, it returns immediately but it may not have its local value updated. The read will return the old value. Causes random failures: {noformat} *StrongCounter.compareAnd*() {noformat} was: A stale read can happen in a backup owner if it performs a [conditional] write follow by a read operation. If the write operation fails, it returns immediately but it may not have its local value updated. The read will return the old value. Causes random failures in {{*StrongCounter.compareAnd*()}} tests. > Inconsistency if the WriteCommand isn't successful (triangle) > ------------------------------------------------------------- > > Key: ISPN-8786 > URL: https://issues.jboss.org/browse/ISPN-8786 > Project: Infinispan > Issue Type: Bug > Components: Core > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > > A stale read can happen in a backup owner if it performs a (conditional) write follow by a read operation. > If the write operation fails, it returns immediately but it may not have its local value updated. The read will return the old value. > Causes random failures: > {noformat} > *StrongCounter.compareAnd*() > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8786) Inconsistency if the WriteCommand isn't successful (triangle)

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-8786?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-8786: ------------------------------ Description: A stale read can happen in a backup owner if it performs a [conditional] write follow by a read operation. If the write operation fails, it returns immediately but it may not have its local value updated. The read will return the old value. Causes random failures in {{*StrongCounter.compareAnd*()}} tests. was: A stale read can happen in a backup owner if it performs a [conditional] write follow by a read operation. If the write operation fails, it returns immediately but it may not have its local value updated. The read will return the old value. > Inconsistency if the WriteCommand isn't successful (triangle) > ------------------------------------------------------------- > > Key: ISPN-8786 > URL: https://issues.jboss.org/browse/ISPN-8786 > Project: Infinispan > Issue Type: Bug > Components: Core > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > > A stale read can happen in a backup owner if it performs a [conditional] write follow by a read operation. > If the write operation fails, it returns immediately but it may not have its local value updated. The read will return the old value. > Causes random failures in {{*StrongCounter.compareAnd*()}} tests. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8757) Cancel Scheduled TryLock requests if they are already done

by Katia Aresti (JIRA)

[ https://issues.jboss.org/browse/ISPN-8757?page=com.atlassian.jira.plugin.... ] Katia Aresti updated ISPN-8757: ------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/5829 > Cancel Scheduled TryLock requests if they are already done > ---------------------------------------------------------- > > Key: ISPN-8757 > URL: https://issues.jboss.org/browse/ISPN-8757 > Project: Infinispan > Issue Type: Enhancement > Components: Clustered Locks > Reporter: Katia Aresti > Assignee: Katia Aresti > > If the users put a vert high timeout, we will have a potential memory issue on the scheduler. > When a tryLock request is done, it scheduler task should be cleaned up -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8893) Stack trace of a primary request of Infinispan is lost, damaging supportability severely

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-8893?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8893: ---------------------------------- Fix Version/s: 8.2.10.Final (was: 8.2.9.Final) > Stack trace of a primary request of Infinispan is lost, damaging supportability severely > ---------------------------------------------------------------------------------------- > > Key: ISPN-8893 > URL: https://issues.jboss.org/browse/ISPN-8893 > Project: Infinispan > Issue Type: Bug > Components: Core > Reporter: Yeray Borges > Assignee: Yeray Borges > Labels: top-50-list > Fix For: 9.2.1.Final, 8.2.10.Final > > > A request is handled by XNIO's "default task-NNN" thread. If the request executes a clustering cache operation, like session replication, it waits for the backup operation on another server. And if the other server failed on the backup operation, the primary server unwraps the exception to print only the remote exception. The original context of thread "default task-NNN" is lost and a user can't even identify what the primary operation was. > This affects supportability too much. It seems only JDG 7.1 is free from this issue (it has {{AsyncInterceptorChain}}). All other releases like EAP 7.1, RHSSO which is based on EAP 7.0 has this issue. > See the "Forum Reference" link of a mail thread for the detail. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-7958) Backports for 8.2.8.Final

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7958?page=com.atlassian.jira.plugin.... ] Tristan Tarrant closed ISPN-7958. --------------------------------- Resolution: Out of Date > Backports for 8.2.8.Final > ------------------------- > > Key: ISPN-7958 > URL: https://issues.jboss.org/browse/ISPN-7958 > Project: Infinispan > Issue Type: Bug > Affects Versions: 8.2.7.Final > Reporter: Radoslav Husar > Fix For: 8.2.9.Final > > > Tracking JIRA for issues to be backported to 8.2.x for 8.2.8.Final. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-7934) CacheImpl should consult EvictionStrategy#isEnabled

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7934?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7934: ---------------------------------- Fix Version/s: (was: 8.2.9.Final) > CacheImpl should consult EvictionStrategy#isEnabled > --------------------------------------------------- > > Key: ISPN-7934 > URL: https://issues.jboss.org/browse/ISPN-7934 > Project: Infinispan > Issue Type: Bug > Affects Versions: 8.2.6.Final, 9.0.1.Final > Reporter: Galder Zamarreño > Assignee: Radoslav Husar > Fix For: 9.0.4.Final, 9.3.0.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6964) Flag is not included in Javadocs

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6964?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6964: ---------------------------------- Fix Version/s: (was: 8.2.9.Final) (was: 9.3.0.Final) > Flag is not included in Javadocs > -------------------------------- > > Key: ISPN-6964 > URL: https://issues.jboss.org/browse/ISPN-6964 > Project: Infinispan > Issue Type: Bug > Components: Documentation-Core > Affects Versions: 8.2.4.Final, 9.0.0.Alpha4 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > > The AdvancedCache javadocs refer to the Flag enumeration, but this is not included in the javadoc. Also DecoratedCache, which should be an internal implementation detail, is referenced as a public API. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-7934) CacheImpl should consult EvictionStrategy#isEnabled

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7934?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7934: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > CacheImpl should consult EvictionStrategy#isEnabled > --------------------------------------------------- > > Key: ISPN-7934 > URL: https://issues.jboss.org/browse/ISPN-7934 > Project: Infinispan > Issue Type: Bug > Affects Versions: 8.2.6.Final, 9.0.1.Final > Reporter: Galder Zamarreño > Assignee: Radoslav Husar > Fix For: 9.0.4.Final, 8.2.9.Final, 9.3.0.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8932) Add dependency-check-maven plugin

by Gustavo Fernandes (JIRA)

Gustavo Fernandes created ISPN-8932: --------------------------------------- Summary: Add dependency-check-maven plugin Key: ISPN-8932 URL: https://issues.jboss.org/browse/ISPN-8932 Project: Infinispan Issue Type: Bug Components: Build Reporter: Gustavo Fernandes Assignee: Gustavo Fernandes -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8931) Clear post notifications can cause memory issues as it holds all entries locally

by William Burns (JIRA)

William Burns created ISPN-8931: ----------------------------------- Summary: Clear post notifications can cause memory issues as it holds all entries locally Key: ISPN-8931 URL: https://issues.jboss.org/browse/ISPN-8931 Project: Infinispan Issue Type: Bug Affects Versions: 9.1.3.Final, 9.2.0.Beta1 Reporter: William Burns Assignee: William Burns Fix For: 9.1.4.Final, 9.2.0.Beta2 Currently clear iterates over the container and stores all entries before finally invoking clear. This can cause memory issues especially for off heap as we don't want to have all of these entries in the JVM heap at the same time. Something like {code} Iterator<InternalCacheEntry<Object, Object>> iterator = dataContainer.iterator(); while (iterator.hasNext()) { InternalCacheEntry entry = iterator.next(); iterator.remove(); notifier.notifyCacheEntryRemoved(entry.getKey(), entry.getValue(), entry.getMetadata(), false, context, command); } {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues March 2018