February 2019 - infinispan-issues

[JBoss JIRA] (ISPN-5929) InfinispanQueryIT.testQueryOnFirstNode random failures

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-5929?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-5929: ---------------------------------- Fix Version/s: 10.0.0.Final (was: 9.4.8.Final) > InfinispanQueryIT.testQueryOnFirstNode random failures > ------------------------------------------------------ > > Key: ISPN-5929 > URL: https://issues.jboss.org/browse/ISPN-5929 > Project: Infinispan > Issue Type: Bug > Components: Integration , Test Suite - Query > Affects Versions: 8.1.0.Alpha2 > Reporter: Dan Berindei > Assignee: Adrian Nistor > Priority: Blocker > Fix For: 10.0.0.Final > > > {{InfinispanQueryIT.testQueryOnFirstNode()}} and {{InfinispanQueryIT.testQueryOnSecondNode()}} fail randomly in CI with this assertion: > {noformat} > java.lang.AssertionError: expected:<3> but was:<2> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:743) > at org.junit.Assert.assertEquals(Assert.java:118) > at org.junit.Assert.assertEquals(Assert.java:555) > at org.junit.Assert.assertEquals(Assert.java:542) > at org.infinispan.test.integration.as.query.InfinispanQueryIT.testQueryOnFirstNode(InfinispanQueryIT.java:99) > {noformat} > Example: http://ci.infinispan.org/viewLog.html?buildId=31810&tab=buildResultsDiv&b... -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5600) Optimize transactions on multiple caches

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-5600?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-5600: ---------------------------------- Fix Version/s: 10.0.0.Final (was: 9.4.8.Final) > Optimize transactions on multiple caches > ---------------------------------------- > > Key: ISPN-5600 > URL: https://issues.jboss.org/browse/ISPN-5600 > Project: Infinispan > Issue Type: Enhancement > Components: Transactions > Affects Versions: 8.0.0.Alpha2 > Reporter: Radim Vansa > Priority: Major > Fix For: 10.0.0.Final > > > NON_XA transactions that span multiple caches are registered as multiple synchronizations, and these synchronizations are often processed sequentially ^1^; therefore, we send synchronous PrepareCommand for each cache and then CommitCommand for each cache as well, delaying the commit by these round-trips. > Since the targets for different caches may differ, we still need to send the RPCs separately, but in parallel. Therefore, there should be one uber-synchronization for all caches that use NON_XA mode (and maybe something similar with XA). I believe that using single synchronization could save some allocations, too. > ^1^ Not sure if full-fledged JTA implementations do that; JTA spec does not say anything about the order of synchronizations and whether these should be processed in parallel. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5578) Allow default index storage location scoped by cache name

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-5578?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-5578: ---------------------------------- Fix Version/s: 10.0.0.Final (was: 9.4.8.Final) > Allow default index storage location scoped by cache name > --------------------------------------------------------- > > Key: ISPN-5578 > URL: https://issues.jboss.org/browse/ISPN-5578 > Project: Infinispan > Issue Type: Feature Request > Components: Embedded Querying > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Major > Fix For: 10.0.0.Final > > > Thus avoiding clashing of multiple indexed caches without necessarily needing to configure {{indexBase}} for each one -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5575) Shared write-behind store can read stale entries on joiner

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-5575?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-5575: ---------------------------------- Fix Version/s: 10.0.0.Final (was: 9.4.8.Final) > Shared write-behind store can read stale entries on joiner > ---------------------------------------------------------- > > Key: ISPN-5575 > URL: https://issues.jboss.org/browse/ISPN-5575 > Project: Infinispan > Issue Type: Bug > Components: Core, Loaders and Stores > Affects Versions: 8.0.0.Alpha2, 7.2.3.Final > Reporter: Dan Berindei > Priority: Major > Fix For: 10.0.0.Final > > > The AsyncCacheWriter modification queue is not sent with state transfer when the store is shared. A joiner can then read from the shared store a stale version of entries that have updates in the modification queue but are no longer in memory (because they were either removed explicitly, or evicted). -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5574) Define high-level cache capabilities

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-5574?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-5574: ---------------------------------- Fix Version/s: 10.0.0.Final (was: 9.4.8.Final) > Define high-level cache capabilities > ------------------------------------ > > Key: ISPN-5574 > URL: https://issues.jboss.org/browse/ISPN-5574 > Project: Infinispan > Issue Type: Feature Request > Components: Configuration, Core > Affects Versions: 7.2.3.Final > Reporter: Dan Berindei > Priority: Minor > Fix For: 10.0.0.Final > > > Infinispan's configuration is very flexible, and it's sometimes hard to figure out how different settings affect things like cache consistency. > For example, the lucene-directory module uses the fairly complicated {{Configurations.noDataLossOnJoiner()}} method to validate that a cache is safe for storing lucene indexes. > Another example is users who would like to use a store for backup, but they don't want read from the store for M/R tasks or when get(k) doesn't find the key in memory. > One idea would be to define a set of "capabilities" like "state-transfer-complete" or "all-data-in-memory". The user could then add those capabilities in the cache definition, and the cache won't start if the configuration violates those capabilities. The capabilities would also be used internally, to improve the error message when a feature requires a particular combination of settings. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6165) Remove Configuration.ssl from HotRod since it is handled by Configuration.security

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-6165?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6165: ---------------------------------- Fix Version/s: 10.0.0.Final (was: 9.4.8.Final) > Remove Configuration.ssl from HotRod since it is handled by Configuration.security > ---------------------------------------------------------------------------------- > > Key: ISPN-6165 > URL: https://issues.jboss.org/browse/ISPN-6165 > Project: Infinispan > Issue Type: Task > Components: Remote Protocols > Reporter: Tristan Tarrant > Assignee: Galder Zamarreño > Priority: Major > Fix For: 10.0.0.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6162) Drop Query.getResultSize() method

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-6162?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6162: ---------------------------------- Fix Version/s: 10.0.0.Final (was: 9.4.8.Final) > Drop Query.getResultSize() method > --------------------------------- > > Key: ISPN-6162 > URL: https://issues.jboss.org/browse/ISPN-6162 > Project: Infinispan > Issue Type: Task > Components: Embedded Querying, Remote Querying > Reporter: Tristan Tarrant > Assignee: Adrian Nistor > Priority: Major > Fix For: 10.0.0.Final > > > Do we keep org.infinispan.query.dsl.Query.getResultSize? Does it return int or long? Return -1 if actual figure unknown/hard to compute? Result size might be non-trivial for non-indexed or hybrid case and will require full scan even for queries with limit. Deprecate it now, remove in ispn 9. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6094) Use security actions to read system properties for configuration

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-6094?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6094: ---------------------------------- Fix Version/s: 10.0.0.Final (was: 9.4.8.Final) > Use security actions to read system properties for configuration > ---------------------------------------------------------------- > > Key: ISPN-6094 > URL: https://issues.jboss.org/browse/ISPN-6094 > Project: Infinispan > Issue Type: Task > Components: Core, Embedded Querying > Affects Versions: 8.1.0.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 10.0.0.Final > > > Infinispan uses system properties for out-of-band settings that weren't deemed important enough to have a proper configuration attribute: > * infinispan.arrays.debug > * infinispan.unsafe.force_multicast > * infinispan.compat (obsolete?) > * infinispan.debugDependencies > * infinispan.stagger.delay (introduced with ISPN-825) > * org.infinispan.query.indexmanager.LockAcquiringBackend.MAX_QUEUE_SIZE > We should use a {{SecurityActions}} class to access these properties instead of {{Boolean.getBoolean()}} and {{Integer.getInteger()}}. We should also document these system properties, and evaluate moving them to the proper configuration. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6084) Continuous query should reject queries with orderBy

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-6084?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6084: ---------------------------------- Fix Version/s: 10.0.0.Final (was: 9.4.8.Final) > Continuous query should reject queries with orderBy > --------------------------------------------------- > > Key: ISPN-6084 > URL: https://issues.jboss.org/browse/ISPN-6084 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying, Remote Querying > Affects Versions: 8.1.0.Final, 8.0.2.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Priority: Minor > Fix For: 10.0.0.Final > > > Current behaviour it that orderBy is silently ignored. Disallowing this and throwing an exception would be preferable. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6219) An interruption during a MassIndexer run should exit early

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-6219?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6219: ---------------------------------- Fix Version/s: 10.0.0.Final (was: 9.4.8.Final) > An interruption during a MassIndexer run should exit early > ---------------------------------------------------------- > > Key: ISPN-6219 > URL: https://issues.jboss.org/browse/ISPN-6219 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Reporter: Sanne Grinovero > Priority: Major > Fix For: 10.0.0.Final > > > Methods like {{IndexUpdater.updateIndex()}} correctly check for interruption state to skip some work but they don't trigger an early exit from the indexing loop so we'd still be consuming all of the data stream. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues February 2019