September 2014 - infinispan-issues

[JBoss JIRA] (ISPN-4643) Make sure EntryIterator doesn't return expired entries

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-4643?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-4643: -------------------------------- Fix Version/s: 7.0.0.CR1 (was: 7.0.0.Beta2) > Make sure EntryIterator doesn't return expired entries > ------------------------------------------------------ > > Key: ISPN-4643 > URL: https://issues.jboss.org/browse/ISPN-4643 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 7.0.0.Beta1 > Reporter: William Burns > Assignee: Dan Berindei > Fix For: 7.0.0.CR1 > > > We should make sure that the entry iterator doesn't return entries that have expired. Since entries can sit in the data container while expired we need to make sure to ignore those. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4633) Local transaction not removed from transaction table after a size() operation

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-4633?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-4633: -------------------------------- Fix Version/s: 7.0.0.CR1 (was: 7.0.0.Beta2) > Local transaction not removed from transaction table after a size() operation > ----------------------------------------------------------------------------- > > Key: ISPN-4633 > URL: https://issues.jboss.org/browse/ISPN-4633 > Project: Infinispan > Issue Type: Bug > Components: Transactions > Affects Versions: 7.0.0.Beta1 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.0.0.CR1 > > > Executing cache.size() as the only operation during a transaction will leave behind a LocalTransaction in the transaction table. This tx has not locked keys and will eventually be removed by the reaper after a while. The same fix as for ISPN-4196 should be applied for size(). -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4677) Map/Reduce job fails with the wrong explanation on underlying TimeoutException

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-4677?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-4677: -------------------------------- Fix Version/s: 7.0.0.CR1 (was: 7.0.0.Beta2) > Map/Reduce job fails with the wrong explanation on underlying TimeoutException > ------------------------------------------------------------------------------ > > Key: ISPN-4677 > URL: https://issues.jboss.org/browse/ISPN-4677 > Project: Infinispan > Issue Type: Bug > Components: Distributed Execution and Map/Reduce > Affects Versions: 7.0.0.Beta1 > Reporter: Sanne Grinovero > Assignee: Vladimir Blagojevic > Fix For: 7.0.0.CR1 > > > I'm running a task which is throwing the following exception during the Map phase: > {noformat} > org.infinispan.util.concurrent.TimeoutException: Node main-NodeC-22183 timed out{noformat} > The user facing error however is this very confusing message: > {noformat}org.infinispan.commons.CacheException: java.util.concurrent.ExecutionException: Map phase executing at main-NodeA-39904 did not complete within 0 sec timeout{noformat} > I have no timeout enabled. > The problem is the instanceof operation on the cause of the error in org.infinispan.distexec.mapreduce.MapReduceTask.executeMapPhaseWithLocalReduction(Map<KOut, VOut>): the check on the type only is not good enough. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4675) Missing server configuration for remote executor thread pool

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-4675?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-4675: -------------------------------- Fix Version/s: 7.0.0.CR1 (was: 7.0.0.Beta2) > Missing server configuration for remote executor thread pool > ------------------------------------------------------------ > > Key: ISPN-4675 > URL: https://issues.jboss.org/browse/ISPN-4675 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 6.0.2.Final, 7.0.0.Beta1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 7.0.0.CR1 > > > The remote commands executor configuration is missing in {{EmbeddedCacheManagerConfigurationService}}. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4664) Consider passing command retries flag to remote events

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-4664?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-4664: -------------------------------- Fix Version/s: 7.0.0.CR1 (was: 7.0.0.Beta2) > Consider passing command retries flag to remote events > ------------------------------------------------------ > > Key: ISPN-4664 > URL: https://issues.jboss.org/browse/ISPN-4664 > Project: Infinispan > Issue Type: Enhancement > Components: Remote Protocols > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 7.0.0.CR1 > > > Cluster listeners have the ability to check whether an event is the result of a retried command. Even though HR clients are notified of failovers via the @ClientCacheFailover annotation, passing on this information could signal that an event is a duplicate or that another event was dropped and replaced (e.g. modified event replaced a created one). -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4660) Cache loader interceptor ignores unsafe.unreliableReturnValues setting

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-4660?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-4660: -------------------------------- Fix Version/s: 7.0.0.CR1 (was: 7.0.0.Beta2) > Cache loader interceptor ignores unsafe.unreliableReturnValues setting > ---------------------------------------------------------------------- > > Key: ISPN-4660 > URL: https://issues.jboss.org/browse/ISPN-4660 > Project: Infinispan > Issue Type: Bug > Components: Core, Loaders and Stores > Affects Versions: 7.0.0.Beta1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Labels: performance > Fix For: 7.0.0.CR1 > > > When {{unsafe.unreliableReturnValues == true}}, we should not try to read the previous value from the loader for non-conditional, non-delta-aware writes. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4682) Improve SyncConsistentHashFactory key distribution

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-4682?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-4682: -------------------------------- Fix Version/s: 7.0.0.CR1 (was: 7.0.0.Beta2) > Improve SyncConsistentHashFactory key distribution > -------------------------------------------------- > > Key: ISPN-4682 > URL: https://issues.jboss.org/browse/ISPN-4682 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Affects Versions: 6.0.2.Final, 7.0.0.Beta1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Labels: performance > Fix For: 7.0.0.CR1, 7.0.0.Final > > > {{SyncConsistentHashFactory}} and {{TopologyAwareSyncConsistentHashFactory}} distribute the segments between nodes randomly, and the number of segments distributed to different nodes is not very even. > They should have a fail-safe mechanism to limit the variation in segment number between nodes. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4681) Preloading from shared cachestore on a new node with non-shared index is skipping indexing

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-4681?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-4681: -------------------------------- Fix Version/s: 7.0.0.CR1 (was: 7.0.0.Beta2) > Preloading from shared cachestore on a new node with non-shared index is skipping indexing > ------------------------------------------------------------------------------------------ > > Key: ISPN-4681 > URL: https://issues.jboss.org/browse/ISPN-4681 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Reporter: Sanne Grinovero > Assignee: Gustavo Fernandes > Fix For: 7.0.0.CR1, 7.0.0.Final > > > We have a test already: {{org.infinispan.query.persistence.SharedCacheLoaderQueryIndexTest}} > It was disabled for other reasons, mistakenly identified as a testsuite error. > The case is simple: the test is configured in such a way to trigger a newly joining node using an in-memory dummy CacheStore which is shared by both nodes, with preloading enabled. > Index storage is not shared though: uses {{ram}}. > During the preload phase of the new node, the preload code issues the {{SKIP_INDEXING}} flag.. which in this case it should not. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4686) Make Infinispan 7.0 binary compatible with 6.x

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-4686?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-4686: -------------------------------- Fix Version/s: 7.0.0.CR1 (was: 7.0.0.Beta2) > Make Infinispan 7.0 binary compatible with 6.x > ---------------------------------------------- > > Key: ISPN-4686 > URL: https://issues.jboss.org/browse/ISPN-4686 > Project: Infinispan > Issue Type: Bug > Affects Versions: 7.0.0.Beta1 > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 7.0.0.CR1 > > > The idea here is to try to produce a Infinispan 7.0 jar that's binary compatible with 6.0 in order to ease upgrading. So far, the following elements have been found to be problematic: > * FileLookupFactory -> FileLookup changes - ISPN-3850 > * JBossStandaloneJTAManagerLookup.init changes - ISPN-3850 > * org.infinispan.AbstractDelegatingAdvancedCache refactoring to org.infinispan.cache.impl.AbstractDelegatingAdvancedCache - ISPN-4074 > XML configuration stays apart since one of the key aspects of 7.0 is to produce WF-like configuration that's as close as possible, to improve usability between library and server mode. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4684) Segments with potentially stale L1 data are not invalidated correctly

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-4684?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-4684: -------------------------------- Fix Version/s: 7.0.0.CR1 (was: 7.0.0.Beta2) > Segments with potentially stale L1 data are not invalidated correctly > --------------------------------------------------------------------- > > Key: ISPN-4684 > URL: https://issues.jboss.org/browse/ISPN-4684 > Project: Infinispan > Issue Type: Bug > Components: Core, State Transfer > Affects Versions: 6.0.2.Final, 7.0.0.Beta1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Critical > Fix For: 7.0.0.CR1 > > > {{StateConsumerImpl.computeStaleL1Entries()}} uses {{newWriteCh}} instead of {{previousWriteCh}}, so the list of stale L1 segments is always empty. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 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 2014