December 2018 - infinispan-issues

[JBoss JIRA] (ISPN-6015) Query DSL should support groupBy for multi-valued properties

by Galder Zamarreño (Jira)

[ https://issues.jboss.org/browse/ISPN-6015?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-6015: ----------------------------------- Fix Version/s: 9.4.5.Final (was: 9.4.4.Final) > Query DSL should support groupBy for multi-valued properties > ------------------------------------------------------------ > > Key: ISPN-6015 > URL: https://issues.jboss.org/browse/ISPN-6015 > Project: Infinispan > Issue Type: Feature Request > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Priority: Major > Fix For: 9.4.5.Final > > > If a groupBy property is multivalued the entity will belong to multiple groups, one for each distinct value. > Current implementation in 8.0.x and 8.1.x does not allow this and instead of providing invalid results grouping by multivalued property was disallowed (see ISPN-6008). -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6011) ClassCastException in CDI generated keys for JCache

by Galder Zamarreño (Jira)

[ https://issues.jboss.org/browse/ISPN-6011?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-6011: ----------------------------------- Fix Version/s: 9.4.5.Final (was: 9.4.4.Final) > ClassCastException in CDI generated keys for JCache > --------------------------------------------------- > > Key: ISPN-6011 > URL: https://issues.jboss.org/browse/ISPN-6011 > Project: Infinispan > Issue Type: Bug > Affects Versions: 8.1.0.CR1, 8.0.2.Final > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Priority: Major > Fix For: 9.4.5.Final > > > When using JCache-annotations the DefaultCacheKeyGenerator exclusively looks at parameter values to form the cache key. Therefore it will be very likely that collissions occur (resulting in difficult to find ClassCastExceptions). The provided patch uses the method- and class names as additionally values to make the cache key more unique. > Might also add that I am aware that by spec this should not be an issue when no cachename is given (as it should generate a cache using the class-name), but when a cache name is given collissions may occur. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5987) Create concurrent topology switch under failover unit test

by Galder Zamarreño (Jira)

[ https://issues.jboss.org/browse/ISPN-5987?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-5987: ----------------------------------- Fix Version/s: 9.4.5.Final (was: 9.4.4.Final) > Create concurrent topology switch under failover unit test > ---------------------------------------------------------- > > Key: ISPN-5987 > URL: https://issues.jboss.org/browse/ISPN-5987 > Project: Infinispan > Issue Type: Task > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Priority: Major > Fix For: 9.4.5.Final > > > Create a unit test for ISPN-5879. > Matej built a very interesting one [here|https://raw.githubusercontent.com/mcimbora/infinispan/da971738e326a7...] but needs some further work. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

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

by Galder Zamarreño (Jira)

[ https://issues.jboss.org/browse/ISPN-5929?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-5929: ----------------------------------- Fix Version/s: 9.4.5.Final (was: 9.4.4.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: 9.4.5.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)

7 years, 4 months

1
0
0 / 0

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

by Galder Zamarreño (Jira)

[ https://issues.jboss.org/browse/ISPN-5600?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-5600: ----------------------------------- Fix Version/s: 9.4.5.Final (was: 9.4.4.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: 9.4.5.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)

7 years, 4 months

1
0
0 / 0

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

by Galder Zamarreño (Jira)

[ https://issues.jboss.org/browse/ISPN-5578?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-5578: ----------------------------------- Fix Version/s: 9.4.5.Final (was: 9.4.4.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: 9.4.5.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)

7 years, 4 months

1
0
0 / 0

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

by Galder Zamarreño (Jira)

[ https://issues.jboss.org/browse/ISPN-5575?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-5575: ----------------------------------- Fix Version/s: 9.4.5.Final (was: 9.4.4.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: 9.4.5.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)

7 years, 4 months

1
0
0 / 0

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

by Galder Zamarreño (Jira)

[ https://issues.jboss.org/browse/ISPN-5574?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-5574: ----------------------------------- Fix Version/s: 9.4.5.Final (was: 9.4.4.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: 9.4.5.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)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5572) Exposed JMX MBeans should be separate components

by Galder Zamarreño (Jira)

[ https://issues.jboss.org/browse/ISPN-5572?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-5572: ----------------------------------- Fix Version/s: 9.4.5.Final (was: 9.4.4.Final) > Exposed JMX MBeans should be separate components > ------------------------------------------------ > > Key: ISPN-5572 > URL: https://issues.jboss.org/browse/ISPN-5572 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 8.0.0.Alpha2, 7.2.3.Final > Reporter: Dan Berindei > Priority: Major > Fix For: 9.4.5.Final > > > We currently expose internal components as JMX MBeans, and that makes our JMX "API" very unstructured. The exposed MBeans should be separate components, and the only concern in their interfaces should be ease of use. > One example of JMX getting in the way of refactoring is {{CacheMgmtInterceptor}}. The interceptor chain is dynamic, so it should be possible to insert the interceptor only when statistics are enabled. But because the {{statisticsEnabled}} attribute is on the interceptor itself, that becomes a lot trickier, and we had to introduce a separate configuration attribute that disables statistics permanently (ISPN-5542). -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5570) Cross-site: retry backup commands

by Galder Zamarreño (Jira)

[ https://issues.jboss.org/browse/ISPN-5570?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-5570: ----------------------------------- Fix Version/s: 9.4.5.Final (was: 9.4.4.Final) > Cross-site: retry backup commands > --------------------------------- > > Key: ISPN-5570 > URL: https://issues.jboss.org/browse/ISPN-5570 > Project: Infinispan > Issue Type: Bug > Components: Core, Cross-Site Replication > Affects Versions: 7.2.3.Final > Reporter: Dan Berindei > Priority: Major > Fix For: 9.4.5.Final > > > There are 3 phases in a backup RPC: > 1. Sender -> Local site master: caused by the site master is shutting down or crashing, or by a network split. > 2. Local site master -> Remote site master: > 2.1. Local site master is no longer a site master, e.g. because it's shutting down or because it's no longer coordinator after a merge. > 2.2. Remote site master is not longer a site master. > 2.3. Link between local site and remote site is down. > 3. Remote site master -> Backup targets > Replication failures in phase 3 are handled by retrying (except for TimeoutExceptions), because {{BaseBackupReceiver}} uses regular cache methods to perform the updates. > But replication failures in phases 1 and 2 are not handled in any way, except for causing the remote site to be taken offline after a certain number of replication failures (if backup is synchronous). We should instead retry backup RPCs when we get a {{SuspectException}} or {{UnreachableException}}, and perhaps even when we get no response (2.2?), and only stop when the timeout expires or when the backup is taken offline. > Async backup probably needs retrying as well, and perhaps even a more sophisticated approach like I-RAC (ISPN-2634). -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 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 December 2018