March 2016 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-6429) Duplicated boolean projections are broken in compat mode

by Adrian Nistor (JIRA)

Adrian Nistor created ISPN-6429: ----------------------------------- Summary: Duplicated boolean projections are broken in compat mode Key: ISPN-6429 URL: https://issues.jboss.org/browse/ISPN-6429 Project: Infinispan Issue Type: Bug Components: Remote Querying Affects Versions: 8.2.0.Final Reporter: Adrian Nistor Assignee: Adrian Nistor Fix For: 9.0.0.Final, 9.0.0.Alpha1, 8.2.1.Final To reproduce: 1. a compat mode, indexed cache. 2. a dsl projection query that selects the same boolean column twice 3. query works ok from embedded side, fails from remote side: the second occurrence of the boolean is actually returned as String. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6428) A [mostly harmless] race condition between RemoveExpiredCommand and cache loaders

by Krzysztof Sobolewski (JIRA)

Krzysztof Sobolewski created ISPN-6428: ------------------------------------------ Summary: A [mostly harmless] race condition between RemoveExpiredCommand and cache loaders Key: ISPN-6428 URL: https://issues.jboss.org/browse/ISPN-6428 Project: Infinispan Issue Type: Quality Risk Components: Core Affects Versions: 8.2.0.Final Reporter: Krzysztof Sobolewski There is a cluster (DIST_SYNC in this particular case) with mortal entries (expiration time, no idle time). I try to update an entry and this is what happens: 1) The local node fetches the entry from its owner(s) 2) Each owner sees that the entry is expired 2a) it loads the entry from cache loader 2b) it schedules an asynchronous RemoveExpiredCommand to be sent across the cluster The RemoveExpiredCommand is meant to opportunistically remove expired entries (in addition to periodically scrubbing the cluster for expired entries), as I understand it. Now two things happen in parallel: 3a) The entry is returned to the initiating node where it is modified and inserted back, the transaction commits and the changes are replicated 3b) The RemoveExpiredCommand gets replicated If the 3b completes before 3a, then the entry is removed from all the owners, where it just had been loaded, before it's forced to load again by changes made by 3a. Now, this is not fatal, it's just inefficient :) But as it happens my code generates an event when the primary owner loads a node and this causes my code to send spurious events in some cases. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-5631) NearCache: ability di wait for other Java HotRod clients to invalidate lazy near cache on remove

by Enrico Olivelli (JIRA)

[ https://issues.jboss.org/browse/ISPN-5631?page=com.atlassian.jira.plugin.... ] Enrico Olivelli commented on ISPN-5631: --------------------------------------- Any news on this issue, isn't it interesting for other users ? > NearCache: ability di wait for other Java HotRod clients to invalidate lazy near cache on remove > ------------------------------------------------------------------------------------------------ > > Key: ISPN-5631 > URL: https://issues.jboss.org/browse/ISPN-5631 > Project: Infinispan > Issue Type: Feature Request > Components: Core > Affects Versions: 7.2.3.Final > Environment: Java hotrod client/server > Reporter: Enrico Olivelli > Labels: hotrod-java-client > > When a Java HotRod client invalidates (remove) an entry it is possibile that this action is not propagated with enough speed to other clients due to the async nature of event notifcations used by NearCache, an so it is possibile that another client looks up a stale entry from its near cache. > A typical "writer client" scenario is: > - update the database and commit the transaction > - invalidate the entry which represents the updated (only a "remove") > The "reader" procedure is: > - lookup in the cache (nearcache, backed by the remote Infinispan cluster) > - in case of "cache miss" perform a lookup on the database and write the entry in the cache -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6417) Remove replication-queue support

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6417?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6417: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Remove replication-queue support > -------------------------------- > > Key: ISPN-6417 > URL: https://issues.jboss.org/browse/ISPN-6417 > Project: Infinispan > Issue Type: Task > Components: Configuration, Core > Affects Versions: 8.2.0.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 9.0.0.Final, 9.0.0.Alpha1 > > > See ISPN-6017 for the motivation. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6423) Move clustering.sync.replTimeout to clustering.remoteTimeout

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6423?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6423: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Move clustering.sync.replTimeout to clustering.remoteTimeout > ------------------------------------------------------------ > > Key: ISPN-6423 > URL: https://issues.jboss.org/browse/ISPN-6423 > Project: Infinispan > Issue Type: Task > Components: Configuration, Core > Affects Versions: 8.2.0.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 9.0.0.Final, 9.0.0.Alpha1 > > > The async configuration is already being removed with ISPN-6417, we should prepare to remove the sync configuration as well (replTimeout is now the only attribute). > The XML configuration already uses a {{remote-timeout}} attribute directly on the cache element, so this change would better align the programmatic and XML configurations. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6427) [Remote Query] Add test for multiple indexed caches using InfinispanIndexManager

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-6427?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-6427: ------------------------------------ Status: Open (was: New) > [Remote Query] Add test for multiple indexed caches using InfinispanIndexManager > -------------------------------------------------------------------------------- > > Key: ISPN-6427 > URL: https://issues.jboss.org/browse/ISPN-6427 > Project: Infinispan > Issue Type: Task > Components: Test Suite - Query > Affects Versions: 8.2.0.Final > Reporter: Gustavo Fernandes > Priority: Minor > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6427) [Remote Query] Add test for multiple indexed caches using InfinispanIndexManager

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-6427?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-6427: ------------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4168 > [Remote Query] Add test for multiple indexed caches using InfinispanIndexManager > -------------------------------------------------------------------------------- > > Key: ISPN-6427 > URL: https://issues.jboss.org/browse/ISPN-6427 > Project: Infinispan > Issue Type: Task > Components: Test Suite - Query > Affects Versions: 8.2.0.Final > Reporter: Gustavo Fernandes > Priority: Minor > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6427) [Remote Query] Add test for multiple indexed caches using InfinispanIndexManager

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-6427?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-6427: ------------------------------------ Affects Version/s: 8.2.0.Final > [Remote Query] Add test for multiple indexed caches using InfinispanIndexManager > -------------------------------------------------------------------------------- > > Key: ISPN-6427 > URL: https://issues.jboss.org/browse/ISPN-6427 > Project: Infinispan > Issue Type: Task > Components: Test Suite - Query > Affects Versions: 8.2.0.Final > Reporter: Gustavo Fernandes > Priority: Minor > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6427) [Remote Query] Add test for multiple indexed caches using InfinispanIndexManager

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-6427?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-6427: ------------------------------------ Priority: Minor (was: Major) > [Remote Query] Add test for multiple indexed caches using InfinispanIndexManager > -------------------------------------------------------------------------------- > > Key: ISPN-6427 > URL: https://issues.jboss.org/browse/ISPN-6427 > Project: Infinispan > Issue Type: Task > Components: Test Suite - Query > Reporter: Gustavo Fernandes > Priority: Minor > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6427) [Remote Query] Add test for multiple indexed caches using InfinispanIndexManager

by Gustavo Fernandes (JIRA)

Gustavo Fernandes created ISPN-6427: --------------------------------------- Summary: [Remote Query] Add test for multiple indexed caches using InfinispanIndexManager Key: ISPN-6427 URL: https://issues.jboss.org/browse/ISPN-6427 Project: Infinispan Issue Type: Task Components: Test Suite - Query Reporter: Gustavo Fernandes -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 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 2016