June 2018 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-5470) Remote-executor threads should not block to acquire locks

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-5470?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-5470: ----------------------------------- Fix Version/s: 9.4.0.Final (was: 9.3.0.Final) > Remote-executor threads should not block to acquire locks > --------------------------------------------------------- > > Key: ISPN-5470 > URL: https://issues.jboss.org/browse/ISPN-5470 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 7.2.1.Final > Reporter: Dan Berindei > Fix For: 9.4.0.Final > > > Currently, enabling the queue on the remote-executor thread pool can cause deadlocks, because a CommitCommand/1PCPrepareCommand could end up in the queue while a remote-executor thread is busy waiting to acquire the same lock that this commit would release. > If trying to acquire a lock would free the thread until the key has been acquired, we could enable the queue on the remote-executor/OOB thread pools, and we would need a lot less threads for the same load. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5453) X-site state transfer: retry locally if local state push throws a SuspectException

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-5453?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-5453: ----------------------------------- Fix Version/s: 9.4.0.Final (was: 9.3.0.Final) > X-site state transfer: retry locally if local state push throws a SuspectException > ---------------------------------------------------------------------------------- > > Key: ISPN-5453 > URL: https://issues.jboss.org/browse/ISPN-5453 > Project: Infinispan > Issue Type: Bug > Components: Core, Cross-Site Replication > Affects Versions: 7.2.1.Final > Reporter: Dan Berindei > Priority: Minor > Fix For: 9.4.0.Final > > > When the local state push command throws a {{SuspectException}}, we currently retry remotely unless the target node was already removed from the cache topology. This will fail with another {{SuspectException}}, so it would be better to retry locally the first time. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 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.0.Final (was: 9.3.0.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.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.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5683) Checkstyle should discover formatting problems

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-5683?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-5683: ----------------------------------- Fix Version/s: 9.4.0.Final (was: 9.3.0.Final) > Checkstyle should discover formatting problems > ---------------------------------------------- > > Key: ISPN-5683 > URL: https://issues.jboss.org/browse/ISPN-5683 > Project: Infinispan > Issue Type: Enhancement > Components: Build > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > Fix For: 9.0.0.Alpha1, 9.4.0.Final > > > Things that should be tested: > * 3 spaces for indent > * space before if -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 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.0.Final (was: 9.3.0.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 > Fix For: 9.4.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.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5585) Guide to Contributing needs updates for Infinispan 8

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-5585?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-5585: ----------------------------------- Fix Version/s: 9.4.0.Final (was: 9.3.0.Final) > Guide to Contributing needs updates for Infinispan 8 > ---------------------------------------------------- > > Key: ISPN-5585 > URL: https://issues.jboss.org/browse/ISPN-5585 > Project: Infinispan > Issue Type: Task > Components: Documentation-Core > Reporter: Sanne Grinovero > Fix For: 9.4.0.Final > > > Just passed the link to a new contributor, I think we should at least update the JDK requirement. > Worth checking the rest.. > http://infinispan.org/docs/8.0.x/contributing/contributing.html -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5579) Infinispan server subsystem thread pool injection

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-5579?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-5579: ----------------------------------- Fix Version/s: 9.4.0.Final (was: 9.3.0.Final) > Infinispan server subsystem thread pool injection > ------------------------------------------------- > > Key: ISPN-5579 > URL: https://issues.jboss.org/browse/ISPN-5579 > Project: Infinispan > Issue Type: Feature Request > Components: Server > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.4.0.Final > > > Upstream wildfly will be dropping the threads subsystem so subsystems which require thread pools should add configuration for these -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 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.0.Final (was: 9.3.0.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 > Fix For: 9.4.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.5.0#75005)

7 years, 9 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.0.Final (was: 9.3.0.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 > Assignee: Dan Berindei > Fix For: 9.4.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.5.0#75005)

7 years, 9 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.0.Final (was: 9.3.0.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.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.5.0#75005)

7 years, 9 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 June 2018