October 2018 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-6169) Drop server support for HotRod 1.x

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-6169?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6169: ---------------------------------- Fix Version/s: 9.4.2.Final (was: 9.4.1.Final) > Drop server support for HotRod 1.x > ---------------------------------- > > Key: ISPN-6169 > URL: https://issues.jboss.org/browse/ISPN-6169 > Project: Infinispan > Issue Type: Task > Components: Remote Protocols, Server > Reporter: Tristan Tarrant > Assignee: Galder Zamarreño > Priority: Major > Fix For: 9.4.2.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6167) Remove deprecated ConsistentHash.init() method from the HotRod client

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-6167?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6167: ---------------------------------- Fix Version/s: 9.4.2.Final (was: 9.4.1.Final) > Remove deprecated ConsistentHash.init() method from the HotRod client > --------------------------------------------------------------------- > > Key: ISPN-6167 > URL: https://issues.jboss.org/browse/ISPN-6167 > Project: Infinispan > Issue Type: Task > Components: Remote Protocols > Reporter: Tristan Tarrant > Assignee: Galder Zamarreño > Priority: Major > Fix For: 9.4.2.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6166) Remove deprecated Near Cache modes

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-6166?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6166: ---------------------------------- Fix Version/s: 9.4.2.Final (was: 9.4.1.Final) > Remove deprecated Near Cache modes > ---------------------------------- > > Key: ISPN-6166 > URL: https://issues.jboss.org/browse/ISPN-6166 > Project: Infinispan > Issue Type: Task > Components: Remote Protocols > Reporter: Tristan Tarrant > Assignee: Galder Zamarreño > Priority: Major > Fix For: 9.4.2.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 1 month

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: 9.4.2.Final (was: 9.4.1.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: 9.4.2.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 1 month

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: 9.4.2.Final (was: 9.4.1.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: 9.4.2.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, 1 month

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: 9.4.2.Final (was: 9.4.1.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: 9.4.2.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, 1 month

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: 9.4.2.Final (was: 9.4.1.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: 9.4.2.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, 1 month

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: 9.4.2.Final (was: 9.4.1.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: 9.4.2.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, 1 month

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: 9.4.2.Final (was: 9.4.1.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: 9.4.2.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, 1 month

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: 9.4.2.Final (was: 9.4.1.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: 9.4.2.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, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues October 2018