June 2017 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-8002) ScatteredStreamIteratorTest.waitUntilProcessingResults random failures

by Dan Berindei (JIRA)

Dan Berindei created ISPN-8002: ---------------------------------- Summary: ScatteredStreamIteratorTest.waitUntilProcessingResults random failures Key: ISPN-8002 URL: https://issues.jboss.org/browse/ISPN-8002 Project: Infinispan Issue Type: Bug Components: Core Affects Versions: 9.1.0.CR1 Reporter: Dan Berindei Assignee: Radim Vansa Priority: Critical Fix For: 9.1.0.Final {noformat} 20:38:39,442 ERROR (testng-Test:[]) [TestSuiteProgress] Test failed: org.infinispan.scattered.stream.ScatteredStreamIteratorTest.waitUntilProcessingResults[SCATTERED_SYNC, tx=false] java.lang.NullPointerException: null at org.infinispan.stream.DistributedStreamIteratorTest.waitUntilProcessingResults(DistributedStreamIteratorTest.java:207) ~[test-classes/:?] {noformat} Looks like segments {{ScatteredVersionManager}} blocks access to segments 10 and 12, and they are never suspected or retried: {noformat} 20:38:38,209 TRACE (remote-thread-Test-NodeBF-p13315-t6:[]) [LocalStreamManagerImpl] Request Test-NodeBD-1062-0 completed segments [6, 7, 13, 14, 15] with [] suspected segments 20:38:38,248 TRACE (async-thread-Test-NodeBD-p13302-t1:[]) [DistributionBulkInterceptor$BackingEntrySet$1] Found [0, 1, 2, 3, 4, 5, 8, 9, 10, 11, 12] lost segments for Test-NodeBD-1062-0 20:38:38,249 TRACE (transport-thread-Test-NodeBD-p13301-t4:[Topology-org.infinispan.scattered.stream.Test]) [ScatteredVersionManager] Node Test-NodeBD-1062 blocks access to segment 10 20:38:38,253 TRACE (async-thread-Test-NodeBD-p13302-t1:[]) [ClusterStreamManagerImpl] Performing remote rehash key aware operations {Test-NodeBF-40292={8-9 11}} for id Test-NodeBD-1062-1 20:38:39,209 TRACE (remote-thread-Test-NodeBF-p13315-t6:[]) [LocalStreamManagerImpl] Request Test-NodeBD-1062-1 completed segments [] with [8, 9, 11] suspected segments 20:38:39,302 TRACE (async-thread-Test-NodeBD-p13302-t1:[]) [DistributionBulkInterceptor$BackingEntrySet$1] Found [0, 1, 2, 3, 4, 5, 8, 9, 11] lost segments for Test-NodeBD-1062-1 20:38:39,420 TRACE (remote-thread-Test-NodeBF-p13315-t6:[]) [LocalStreamManagerImpl] Request Test-NodeBD-1062-2 completed segments [8, 9, 11] with [] suspected segments 20:38:39,436 TRACE (async-thread-Test-NodeBD-p13302-t1:[]) [DistributionBulkInterceptor$BackingEntrySet$1] Completing segments [0, 1, 2, 3, 4, 5] 20:38:39,436 TRACE (async-thread-Test-NodeBD-p13302-t1:[]) {noformat} Please also add a {{toString()}} method in the stream commands, seeing the segments in the requests and responses would make it easier to follow the logs. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7998) Multi-key write commands assume all segments have CH.getNumOwners() owners

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-7998?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-7998: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/5251 > Multi-key write commands assume all segments have CH.getNumOwners() owners > -------------------------------------------------------------------------- > > Key: ISPN-7998 > URL: https://issues.jboss.org/browse/ISPN-7998 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.1.0.Beta1, 9.0.3.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 9.1.0.Final > > > When handling multi-key write commands, both {{TriangleDistributionInterceptor}} and {{NonTxDistributionInterceptor}} assume that there are no backup owners when {{consistentHash.getNumOwners() == 1}}. But during rebalance some segments can have more than {{getNumOwners()}} owners, as the write CH is a union of the current and future CHs, while {{getNumOwners()}} always returns the value in the cache configuration. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7998) Multi-key write commands assume all segments have CH.getNumOwners() owners

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-7998?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-7998: -------------------------------- Fix Version/s: 9.1.0.Final (was: 9.1.0.CR1) > Multi-key write commands assume all segments have CH.getNumOwners() owners > -------------------------------------------------------------------------- > > Key: ISPN-7998 > URL: https://issues.jboss.org/browse/ISPN-7998 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.1.0.Beta1, 9.0.3.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 9.1.0.Final > > > When handling multi-key write commands, both {{TriangleDistributionInterceptor}} and {{NonTxDistributionInterceptor}} assume that there are no backup owners when {{consistentHash.getNumOwners() == 1}}. But during rebalance some segments can have more than {{getNumOwners()}} owners, as the write CH is a union of the current and future CHs, while {{getNumOwners()}} always returns the value in the cache configuration. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6245) Remote query should be able to work with JBoss marshaling, compat mode and hibernate-search annotations

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-6245?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-6245: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Remote query should be able to work with JBoss marshaling, compat mode and hibernate-search annotations > ------------------------------------------------------------------------------------------------------- > > Key: ISPN-6245 > URL: https://issues.jboss.org/browse/ISPN-6245 > Project: Infinispan > Issue Type: Enhancement > Components: Remote Querying > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.1.0.CR1, 9.1.0.Final > > > This currently requires protobuf marshalling but it should be possible to make it work with JBoss marshalling too. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6334) Handle definitions of indexable classes in server config

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-6334?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-6334: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Handle definitions of indexable classes in server config > --------------------------------------------------------- > > Key: ISPN-6334 > URL: https://issues.jboss.org/browse/ISPN-6334 > Project: Infinispan > Issue Type: Feature Request > Components: Remote Querying > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.1.0.CR1, 9.1.0.Final > > > Server's xml config already accepts them but they are not actually used. This is a continuation of ISPN-6178. Tests for server are also missing ATM. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6334) Handle definitions of indexable classes in server config

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6334?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-6334: -------------------------------- Fix Version/s: 9.1.0.CR1 > Handle definitions of indexable classes in server config > --------------------------------------------------------- > > Key: ISPN-6334 > URL: https://issues.jboss.org/browse/ISPN-6334 > Project: Infinispan > Issue Type: Feature Request > Components: Remote Querying > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.1.0.CR1, 9.1.0.Final > > > Server's xml config already accepts them but they are not actually used. This is a continuation of ISPN-6178. Tests for server are also missing ATM. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6245) Remote query should be able to work with JBoss marshaling, compat mode and hibernate-search annotations

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6245?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-6245: -------------------------------- Fix Version/s: 9.1.0.CR1 > Remote query should be able to work with JBoss marshaling, compat mode and hibernate-search annotations > ------------------------------------------------------------------------------------------------------- > > Key: ISPN-6245 > URL: https://issues.jboss.org/browse/ISPN-6245 > Project: Infinispan > Issue Type: Enhancement > Components: Remote Querying > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.1.0.CR1, 9.1.0.Final > > > This currently requires protobuf marshalling but it should be possible to make it work with JBoss marshalling too. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8001) HotRodCustomMarshallerIteratorIT fails randomly

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-8001?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-8001: -------------------------------- Description: There seems to be a race condition between the execution of the test and the deployment on the marshaller. {code} ------------------------------------------------------------------------------- Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.355 sec <<< FAILURE! - in org.infinispan.server.test.client.hotrod.HotRodCustomMarshallerIteratorIT testIteration(org.infinispan.server.test.client.hotrod.HotRodCustomMarshallerIteratorIT) Time elapsed: 0.103 sec <<< ERROR! org.infinispan.client.hotrod.exceptions.HotRodClientException: java.io.IOException: Unsupported protocol version 40 at org.infinispan.client.hotrod.impl.protocol.Codec20.checkForErrorsInResponseStatus(Codec20.java:363) at org.infinispan.client.hotrod.impl.protocol.Codec20.readPartialHeader(Codec20.java:152) at org.infinispan.client.hotrod.impl.protocol.Codec20.readHeader(Codec20.java:138) at org.infinispan.client.hotrod.impl.operations.HotRodOperation.readHeaderAndValidate(HotRodOperation.java:60) at org.infinispan.client.hotrod.impl.operations.IterationNextOperation.execute(IterationNextOperation.java:51) at org.infinispan.client.hotrod.impl.iteration.RemoteCloseableIterator.fetch(RemoteCloseableIterator.java:104) at org.infinispan.client.hotrod.impl.iteration.RemoteCloseableIterator.hasNext(RemoteCloseableIterator.java:88) at org.infinispan.server.test.client.hotrod.HotRodCustomMarshallerIteratorIT.iteratorToMap(HotRodCustomMarshallerIteratorIT.java:145) at org.infinispan.server.test.client.hotrod.HotRodCustomMarshallerIteratorIT.testIteration(HotRodCustomMarshallerIteratorIT.java:132) {code} > HotRodCustomMarshallerIteratorIT fails randomly > ----------------------------------------------- > > Key: ISPN-8001 > URL: https://issues.jboss.org/browse/ISPN-8001 > Project: Infinispan > Issue Type: Bug > Affects Versions: 9.1.0.Beta1 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.1.0.Final > > > There seems to be a race condition between the execution of the test and the deployment on the marshaller. > {code} > ------------------------------------------------------------------------------- > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.355 sec <<< FAILURE! - in org.infinispan.server.test.client.hotrod.HotRodCustomMarshallerIteratorIT > testIteration(org.infinispan.server.test.client.hotrod.HotRodCustomMarshallerIteratorIT) Time elapsed: 0.103 sec <<< ERROR! > org.infinispan.client.hotrod.exceptions.HotRodClientException: java.io.IOException: Unsupported protocol version 40 > at org.infinispan.client.hotrod.impl.protocol.Codec20.checkForErrorsInResponseStatus(Codec20.java:363) > at org.infinispan.client.hotrod.impl.protocol.Codec20.readPartialHeader(Codec20.java:152) > at org.infinispan.client.hotrod.impl.protocol.Codec20.readHeader(Codec20.java:138) > at org.infinispan.client.hotrod.impl.operations.HotRodOperation.readHeaderAndValidate(HotRodOperation.java:60) > at org.infinispan.client.hotrod.impl.operations.IterationNextOperation.execute(IterationNextOperation.java:51) > at org.infinispan.client.hotrod.impl.iteration.RemoteCloseableIterator.fetch(RemoteCloseableIterator.java:104) > at org.infinispan.client.hotrod.impl.iteration.RemoteCloseableIterator.hasNext(RemoteCloseableIterator.java:88) > at org.infinispan.server.test.client.hotrod.HotRodCustomMarshallerIteratorIT.iteratorToMap(HotRodCustomMarshallerIteratorIT.java:145) > at org.infinispan.server.test.client.hotrod.HotRodCustomMarshallerIteratorIT.testIteration(HotRodCustomMarshallerIteratorIT.java:132) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8001) HotRodCustomMarshallerIteratorIT fails randomly

by Adrian Nistor (JIRA)

Adrian Nistor created ISPN-8001: ----------------------------------- Summary: HotRodCustomMarshallerIteratorIT fails randomly Key: ISPN-8001 URL: https://issues.jboss.org/browse/ISPN-8001 Project: Infinispan Issue Type: Bug Affects Versions: 9.1.0.Beta1 Reporter: Adrian Nistor Assignee: Adrian Nistor Fix For: 9.1.0.Final -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8001) HotRodCustomMarshallerIteratorIT fails randomly

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-8001?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-8001: -------------------------------- Status: Open (was: New) > HotRodCustomMarshallerIteratorIT fails randomly > ----------------------------------------------- > > Key: ISPN-8001 > URL: https://issues.jboss.org/browse/ISPN-8001 > Project: Infinispan > Issue Type: Bug > Affects Versions: 9.1.0.Beta1 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.1.0.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues June 2017