February 2019 - infinispan-issues

[JBoss JIRA] (ISPN-7606) DistributedExecutorMassIndexer.executeInternal should use an existing pool

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-7606?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7606: ---------------------------------- Fix Version/s: 10.0.0.Final (was: 9.4.8.Final) > DistributedExecutorMassIndexer.executeInternal should use an existing pool > -------------------------------------------------------------------------- > > Key: ISPN-7606 > URL: https://issues.jboss.org/browse/ISPN-7606 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Affects Versions: 9.0.0.CR2 > Reporter: Dan Berindei > Assignee: Gustavo Fernandes > Priority: Major > Fix For: 10.0.0.Final > > > {{DistributedExecutorMassIndexer.executeInternal}} creates 2 executors: > 1. {{new DefaultExecutorService(cache)}} implicitly creates a single-threaded executor to run tasks on the local node. > 2. {{compositeFuture.whenCompleteAsync(consumer, Executors.newSingleThreadExecutor())}} explicitly creates a new single-threaded executor to run the consumer on. > Neither of these executors are shut down, and rather than complicating the code to stop them properly it would be better to use an existing executor. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7590) Invocation idempotence

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-7590?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7590: ---------------------------------- Fix Version/s: 10.0.0.Final (was: 9.4.8.Final) > Invocation idempotence > ---------------------- > > Key: ISPN-7590 > URL: https://issues.jboss.org/browse/ISPN-7590 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 9.0.0.CR2 > Reporter: Radim Vansa > Assignee: Radim Vansa > Priority: Major > Labels: consistency > Fix For: 10.0.0.Final > > > This is an umbrella JIRA to change the way how we deal with retries after topology change. > Please link any outstanding issues that refer to incorrect return values of command during topology change. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7470) Distributed executor does not fail over unless future.get() is called

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-7470?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7470: ---------------------------------- Fix Version/s: 10.0.0.Final (was: 9.4.8.Final) > Distributed executor does not fail over unless future.get() is called > --------------------------------------------------------------------- > > Key: ISPN-7470 > URL: https://issues.jboss.org/browse/ISPN-7470 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 8.2.6.Final, 9.0.0.CR1 > Reporter: Dan Berindei > Assignee: William Burns > Priority: Major > Fix For: 10.0.0.Final > > > After ISPN-6392, {{DistributedExecutorService.submit(...)}} nominally returns a {{CompletableFuture}}. However, it doesn't behave like a regular {{CompletableFuture}}, because it doesn't run the failure policy until the user calls {{future.get()}}. > {{future.isComplete()}} will return {{true}} before running the failure policy, and {{future.whenComplete(callback)}} will also execute the callback before running the failure policy. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7415) Immortal entries use EmbeddedExpirableMetadata instead of EmbeddedMetadata

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-7415?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7415: ---------------------------------- Fix Version/s: 10.0.0.Final (was: 9.4.8.Final) > Immortal entries use EmbeddedExpirableMetadata instead of EmbeddedMetadata > -------------------------------------------------------------------------- > > Key: ISPN-7415 > URL: https://issues.jboss.org/browse/ISPN-7415 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.0.0.Beta2 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 10.0.0.Final > > > The default lifespan and maxIdle are -1 to signal no expiration, but calling {{EmbeddedMetadata.Builder.lifespan\(x)}} with any value will make it create an {{EmbeddedExpirableMetadata}} instance. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7302) ClusteredConditionalCommandTest.testPutIfAbsentOnNonOwnerWithIgnoreReturnValues random failures

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-7302?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7302: ---------------------------------- Fix Version/s: 10.0.0.Final (was: 9.4.8.Final) > ClusteredConditionalCommandTest.testPutIfAbsentOnNonOwnerWithIgnoreReturnValues random failures > ----------------------------------------------------------------------------------------------- > > Key: ISPN-7302 > URL: https://issues.jboss.org/browse/ISPN-7302 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 9.0.0.Beta1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Critical > Labels: testsuite_stability > Fix For: 10.0.0.Final > > > When the backup owner replies before the primary had a chance to load the value from persistence, the number of loads from the primary can be {{0}} at the time the test checks it. > {noformat} > 00:21:48,941 TRACE (testng-Test:[]) [JGroupsTransport] dests=[Test-NodeB-56150, Test-NodeA-13512], command=ClusteredGetCommand{key=Test-key, flags=[IGNORE_RETURN_VALUES]}, mode=WAIT_FOR_VALID_RESPONSE, timeout=15000 > 00:21:48,942 TRACE (jgroups-7,Test-NodeB-56150:[]) [InvocationContextInterceptor] Invoked with command GetCacheEntryCommand {key=Test-key, flags=[SKIP_REMOTE_LOOKUP, IGNORE_RETURN_VALUES]} and InvocationContext [org.infinispan.context.impl.NonTxInvocationContext@5f931934] > 00:21:48,943 TRACE (jgroups-7,Test-NodeB-56150:[]) [EntryFactoryImpl] Wrap Test-key for read. Entry=NullCacheEntry{} > 00:21:48,946 TRACE (jgroups-8,Test-NodeA-13512:[]) [InvocationContextInterceptor] Invoked with command GetCacheEntryCommand {key=Test-key, flags=[SKIP_REMOTE_LOOKUP, IGNORE_RETURN_VALUES]} and InvocationContext [org.infinispan.context.impl.NonTxInvocationContext@265c6c97] > 00:21:48,946 TRACE (jgroups-8,Test-NodeA-13512:[]) [PersistenceUtil] Loaded MarshalledEntryImpl{keyBytes=null, valueBytes=null, metadataBytes=null, key=Test-key, value=Test-value1, metadata=null, marshaller=org.infinispan.marshall.core.GlobalMarshaller@1aee2408} for key Test-key from persistence. > 00:21:48,946 TRACE (jgroups-8,Test-NodeA-13512:[]) [CommandAwareRpcDispatcher] About to send back response SuccessfulResponse{responseValue=ImmortalCacheValue {value=Test-value1}} for command ClusteredGetCommand{key=Test-key, flags=[IGNORE_RETURN_VALUES]} > 00:21:48,948 ERROR (testng-Test:[]) [TestSuiteProgress] Test failed: org.infinispan.persistence.ClusteredTxConditionalCommandTest.testPutIfAbsentOnNonOwnerWithIgnoreReturnValues[tx=true] > java.lang.AssertionError: primary owner load expected:<1> but was:<0> > at org.testng.AssertJUnit.fail(AssertJUnit.java:59) ~[testng-6.8.8.jar:?] > at org.testng.AssertJUnit.failNotEquals(AssertJUnit.java:364) ~[testng-6.8.8.jar:?] > at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:80) ~[testng-6.8.8.jar:?] > at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:170) ~[testng-6.8.8.jar:?] > at org.infinispan.persistence.ClusteredTxConditionalCommandTest.assertLoadAfterOperation(ClusteredTxConditionalCommandTest.java:46) ~[test-classes/:?] > at org.infinispan.persistence.ClusteredConditionalCommandTest.doTest(ClusteredConditionalCommandTest.java:121) ~[test-classes/:?] > at org.infinispan.persistence.ClusteredConditionalCommandTest.testPutIfAbsentOnNonOwnerWithIgnoreReturnValues(ClusteredConditionalCommandTest.java:242) ~[test-classes/:?] > 00:21:48,953 TRACE (jgroups-7,Test-NodeB-56150:[]) [PersistenceUtil] Loaded null for key Test-key from persistence. > 00:21:48,953 TRACE (jgroups-7,Test-NodeB-56150:[]) [CommandAwareRpcDispatcher] About to send back response SuccessfulResponse{responseValue=null} for command ClusteredGetCommand{key=Test-key, flags=[IGNORE_RETURN_VALUES]} > {noformat} > Possible fix: replace {{assertEquals}} with {{eventuallyEquals}}. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7288) Indexed queries with IN clause should use TermsQuery

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-7288?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7288: ---------------------------------- Fix Version/s: 10.0.0.Final (was: 9.4.8.Final) > Indexed queries with IN clause should use TermsQuery > ---------------------------------------------------- > > Key: ISPN-7288 > URL: https://issues.jboss.org/browse/ISPN-7288 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying > Affects Versions: 8.2.5.Final, 9.0.0.Beta1 > Reporter: Gustavo Fernandes > Assignee: Adrian Nistor > Priority: Major > Fix For: 10.0.0.Final > > > There are two reasons for it: > * TermsQuery don't have a clause limit as Boolean Queries do (default is 1024) > * Performance for high number of clauses is vastly superior -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7167) ExampleConfigsIT.testTopologyConfigRackAttribute random failures

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-7167?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7167: ---------------------------------- Fix Version/s: 10.0.0.Final (was: 9.4.8.Final) > ExampleConfigsIT.testTopologyConfigRackAttribute random failures > ----------------------------------------------------------------- > > Key: ISPN-7167 > URL: https://issues.jboss.org/browse/ISPN-7167 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Server > Affects Versions: 9.0.0.Alpha4 > Reporter: Dan Berindei > Priority: Critical > Labels: testsuite_stability > Fix For: 10.0.0.Final > > > {noformat} > java.lang.AssertionError: Unexpected number of entries in server1: 0 > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.infinispan.server.test.configs.ExampleConfigsIT.verifyTopologyHinting(ExampleConfigsIT.java:482) > at org.infinispan.server.test.configs.ExampleConfigsIT.testTopologyConfigRackAttribute(ExampleConfigsIT.java:419) > {noformat} > The test is also inconsistent about the names of the servers, sometimes it starts counting from 0 and sometimes it starts counting from 1. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7159) CompleteShutdownDistRetryTest.testRetryAfterCompleteShutdown random failures

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-7159?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7159: ---------------------------------- Fix Version/s: 10.0.0.Final (was: 9.4.8.Final) > CompleteShutdownDistRetryTest.testRetryAfterCompleteShutdown random failures > ---------------------------------------------------------------------------- > > Key: ISPN-7159 > URL: https://issues.jboss.org/browse/ISPN-7159 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Server > Affects Versions: 9.0.0.Alpha4 > Reporter: Dan Berindei > Priority: Critical > Labels: testsuite_stability > Fix For: 10.0.0.Final > > > {noformat} > java.lang.AssertionError: expected:<two> but was:<null> > at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:101) > at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:108) > at org.infinispan.client.hotrod.retry.CompleteShutdownDistRetryTest.testRetryAfterCompleteShutdown(CompleteShutdownDistRetryTest.java:58) > {noformat} > I think the problem is that killing node 0 can make node 2's key move from node 2 to node 1, and then it's lost after node 1 is also killed. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7801) RehashWithL1Test.testPutWithRehashAndCacheClear random failures

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-7801?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7801: ---------------------------------- Fix Version/s: 10.0.0.Final (was: 9.4.8.Final) > RehashWithL1Test.testPutWithRehashAndCacheClear random failures > --------------------------------------------------------------- > > Key: ISPN-7801 > URL: https://issues.jboss.org/browse/ISPN-7801 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 9.0.0.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Labels: testsuite_stability > Fix For: 10.0.0.Final > > > The test kills the only owner of a key and checks that when a node starts owning an L1 entry, it doesn't send it to other nodes during state transfer. Then it adds a new node (owning the key) and checks that the key isn't transferred to the new node, and it's deleted from L1 on the old nodes. The problem is that it doesn't wait, it assumes all the nodes have already removed it by the time {{getCache()}} returns on the joiner. > {noformat} > 03:24:27,606 TRACE (jgroups-5,Test-NodeB-54331:[]) [L1WriteSynchronizer] Caching remotely retrieved entry for key k0 in L1 > 03:24:27,607 TRACE (jgroups-5,Test-NodeB-54331:[]) [DefaultDataContainer] Store MortalCacheEntry{key=k0, value=some data} in container > 03:24:26,754 DEBUG (testng-Test:[]) [Test] Populating L1 on Test-NodeA-2588 > 03:24:27,514 DEBUG (testng-Test:[]) [Test] Populating L1 on Test-NodeB-54331 > 03:24:27,777 DEBUG (testng-Test:[]) [Test] Populating L1 on Test-NodeC-65326 > 03:24:27,777 DEBUG (testng-Test:[]) [Test] Killing node Test-NodeC-65326 > 03:24:27,781 TRACE (transport-thread-Test-NodeA-p51-t2:[Topology-___defaultcache]) [DefaultDataContainer] Removed MortalCacheEntry{key=k0, value=some data} from container > *** The entry is not removed from NodeB at this point > 03:24:27,936 DEBUG (testng-Test:[]) [Test] Checking values on Test-NodeA-2588 > 03:24:27,998 TRACE (jgroups-5,Test-NodeB-54331:[]) [CommandAwareRpcDispatcher] About to send back response SuccessfulResponse{responseValue=MortalCacheValue{value=some data, lifespan=600000, created=1493943867607}} for command ClusteredGetCommand{key=k0, flags=[]} > 03:24:28,034 TRACE (jgroups-7,Test-NodeA-2588:[]) [L1WriteSynchronizer] Caching remotely retrieved entry for key k0 in L1 > 03:24:28,044 TRACE (jgroups-7,Test-NodeA-2588:[]) [DefaultDataContainer] Store MortalCacheEntry{key=k0, value=some data} in container > 03:24:28,519 DEBUG (testng-Test:[]) [Test] Checking values on Test-NodeB-54331 > 03:24:28,595 DEBUG (testng-Test:[]) [Test] Starting a new joiner > 03:24:30,261 TRACE (transport-thread-Test-NodeA-p51-t6:[Topology-___defaultcache]) [InvocationContextInterceptor] Invoked with command InvalidateCommand{keys=[k0, k1, k2, k3, k4, k5, k6, k7, k8, k9]} and InvocationContext [org.infinispan.context.impl.NonTxInvocationContext@54c5cc1d] > 03:24:30,292 DEBUG (testng-Test:[]) [Test] Checking values on Test-NodeA-2588 > 03:24:30,355 ERROR (testng-Test:[]) [TestSuiteProgress] Test failed: org.infinispan.distribution.rehash.RehashWithL1Test.testPutWithRehashAndCacheClear > java.lang.AssertionError: wrong value for k0 > at org.testng.AssertJUnit.fail(AssertJUnit.java:59) ~[testng-6.8.8.jar:?] > at org.testng.AssertJUnit.assertTrue(AssertJUnit.java:24) ~[testng-6.8.8.jar:?] > at org.testng.AssertJUnit.assertNull(AssertJUnit.java:282) ~[testng-6.8.8.jar:?] > at org.infinispan.distribution.rehash.RehashWithL1Test.testPutWithRehashAndCacheClear(RehashWithL1Test.java:78) ~[test-classes/:?] > *** Too late > 03:24:30,360 TRACE (transport-thread-Test-NodeA-p51-t6:[Topology-___defaultcache]) [DefaultDataContainer] Removed MortalCacheEntry{key=k0, value=some data} from container > {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7775) AdminOperationHandler for Domain server mode

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-7775?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7775: ---------------------------------- Fix Version/s: 10.0.0.Final (was: 9.4.8.Final) > AdminOperationHandler for Domain server mode > -------------------------------------------- > > Key: ISPN-7775 > URL: https://issues.jboss.org/browse/ISPN-7775 > Project: Infinispan > Issue Type: Sub-task > Components: Server > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > 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

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues February 2019