December 2019 - infinispan-issues

[JBoss JIRA] (ISPN-2575) KeyTransformer registration is required on all nodes of the cluster, in case of custom keys

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2575?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2575: -------------------------------- Assignee: Adrian Nistor (was: Sanne Grinovero) > KeyTransformer registration is required on all nodes of the cluster, in case of custom keys > ------------------------------------------------------------------------------------------- > > Key: ISPN-2575 > URL: https://issues.jboss.org/browse/ISPN-2575 > Project: Infinispan > Issue Type: Enhancement > Components: Querying > Affects Versions: 5.2.0.Beta5 > Reporter: Anna Manukyan > Assignee: Adrian Nistor > Attachments: ClusteredCacheTest.java > > > The case is the following: > I have a clustered cache on which I want to perform a search. I'm doing the following: > I'm initializing SearchManager on node1, I'm registering a custom key transformer for my key using the created searchmanager, but then when I'm trying to put data into the cache on node1 (which is in REPL_SYNC mode with cache on node2), I'm getting the exception: > java.lang.IllegalArgumentException: Indexing only works with entries keyed on Strings, primitives and classes that have the @Transformable annotation - you passed in a class org.infinispan.query.test.CustomKey3. Alternatively, see org.infinispan.query.SearchManager#registerKeyTransformer > When I'm initializing the SearchManager using node2 cache and register the keyTransformer on it as well, then everything works perfectly, even though I am not using the second created SearchManager. > The test which reproduces the issue is attached to the jira. Please see the test case: testSearchKeyTransformer() -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

4 days, 6 hours

2
1
0 / 0

[JBoss JIRA] (ISPN-11115) Infinispan BOM should only have dependency management for its own artifacts

by Stéphane Nicoll (Jira)

Stéphane Nicoll created ISPN-11115: -------------------------------------- Summary: Infinispan BOM should only have dependency management for its own artifacts Key: ISPN-11115 URL: https://issues.redhat.com/browse/ISPN-11115 Project: Infinispan Issue Type: Bug Components: Build Affects Versions: 10.1.0.Final Reporter: Stéphane Nicoll A BOM should usually have dependency management for the artifacts of the project. Any attempt to provide dependency management for third party artifacts can lead to clashes and warnings in Maven when two boms compete for the same artifact. Could you please consider removing dependency management for the transaction and cache API please? -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10085) Hibernate51 and Hibernate53 should not report the same test name

by Dan Berindei (Jira)

[ https://issues.redhat.com/browse/ISPN-10085?page=com.atlassian.jira.plugi... ] Dan Berindei updated ISPN-10085: -------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/7707, https://github.com/infinispan/infinispan/pull/7710 (was: https://github.com/infinispan/infinispan/pull/7707/files) > Hibernate51 and Hibernate53 should not report the same test name > ---------------------------------------------------------------- > > Key: ISPN-10085 > URL: https://issues.redhat.com/browse/ISPN-10085 > Project: Infinispan > Issue Type: Bug > Components: Test Suite > Affects Versions: 9.4.11.Final, 10.0.0.Final, 10.1.0.Final > Reporter: Diego Lovison > Assignee: Diego Lovison > Priority: Critical > > infinispan-hibernate-cache-v51 and infinispan-hibernate-cache-v53 are using the same tests. Let's say that v51 run first and the test has one error. when running with v53, the test result will be overwritten in the "Test Result" Jenkins plugin because they have the same name, arguments and class name. > the example is here > https://ci.infinispan.org/job/Infinispan/job/PR-6731/13/testReport/org.in... > is it a test for v51 or v53? -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11078) Accept external server file configuration on InfinispanServerRuleBuilder

by Dan Berindei (Jira)

[ https://issues.redhat.com/browse/ISPN-11078?page=com.atlassian.jira.plugi... ] Dan Berindei updated ISPN-11078: -------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 11.0.0.Final 10.1.1.Final Resolution: Done > Accept external server file configuration on InfinispanServerRuleBuilder > ------------------------------------------------------------------------ > > Key: ISPN-11078 > URL: https://issues.redhat.com/browse/ISPN-11078 > Project: Infinispan > Issue Type: Bug > Components: Test Suite > Affects Versions: 10.1.0.CR1 > Reporter: Gustavo Lira e Silva > Assignee: Gustavo Lira e Silva > Priority: Major > Fix For: 11.0.0.Final, 10.1.1.Final > > > Currently InfinispanServerDriver it's only accepting server configuration file using relative path to the project. > We need to be able to use InfinispanServerRule externally like jdg-functional-tests project and we should be able to use full path to the server configuration file -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11113) ScatteredDelayedAvailabilityUpdateTest takes too long

by Dan Berindei (Jira)

[ https://issues.redhat.com/browse/ISPN-11113?page=com.atlassian.jira.plugi... ] Dan Berindei updated ISPN-11113: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/7708 > ScatteredDelayedAvailabilityUpdateTest takes too long > ----------------------------------------------------- > > Key: ISPN-11113 > URL: https://issues.redhat.com/browse/ISPN-11113 > Project: Infinispan > Issue Type: Bug > Components: Core, Test Suite > Affects Versions: 10.1.0.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Minor > Fix For: 11.0.0.Final, 10.1.1.Final > > > Partition handling tests use {{LOCAL_PING.setClusterName()}} with a unique name to disable discovery, otherwise partitions would try to merge while they are supposed to stay separate. > But {{LOCAL_PING}} uses the cluster name on stop to remove the node from the static discovery map. If the test doesn't change the cluster name back, {{LOCAL_PING}} doesn't remove the node, the next test method sees an existing coordinator, and tries to connect to it. When a test has lots of test methods, like {{ScatteredDelayedAvailabilityUpdateTest}}, each test method leaves one more coordinator in the discovery map, and each test method takes longer to start the first method. > {noformat} > 09:08:52,758 DEBUG (testng:[]) [GMS] address=NodeA-30899, cluster=org.infinispan.partitionhandling.ScatteredDelayedAvailabilityUpdateTest[SCATTERED_SYNC, bias=NEVER, DENY_READ_WRITES], physical address=127.0.0.1:51941 > 09:08:52,774 TRACE (testng:[]) [GMS] NodeA-30899: discovery took 0 ms, members: 21 rsps (5 coords) [done] > 09:08:52,774 DEBUG (testng:[]) [GMS] NodeA-30899: found multiple coords: [NodeA-2608, NodeA-5606, NodeA-17288, NodeA-64297, NodeA-48475] > 09:08:52,774 DEBUG (testng:[]) [GMS] NodeA-30899: sending JOIN(NodeA-30899) to NodeA-5606 > 09:08:54,774 WARN (testng:[]) [GMS] NodeA-30899: JOIN(NodeA-30899) sent to NodeA-5606 timed out (after 2000 ms), on try 0 > 09:08:54,774 DEBUG (testng:[]) [GMS] NodeA-30899: sending JOIN(NodeA-30899) to NodeA-64297 > 09:08:56,775 WARN (testng:[]) [GMS] NodeA-30899: JOIN(NodeA-30899) sent to NodeA-64297 timed out (after 2000 ms), on try 0 > 09:08:56,775 DEBUG (testng:[]) [GMS] NodeA-30899: sending JOIN(NodeA-30899) to NodeA-48475 > 09:08:58,775 WARN (testng:[]) [GMS] NodeA-30899: JOIN(NodeA-30899) sent to NodeA-48475 timed out (after 2000 ms), on try 0 > 09:08:58,775 DEBUG (testng:[]) [GMS] NodeA-30899: sending JOIN(NodeA-30899) to NodeA-17288 > 09:09:00,776 WARN (testng:[]) [GMS] NodeA-30899: JOIN(NodeA-30899) sent to NodeA-17288 timed out (after 2000 ms), on try 0 > 09:09:00,776 DEBUG (testng:[]) [GMS] NodeA-30899: sending JOIN(NodeA-30899) to NodeA-2608 > 09:09:02,776 WARN (testng:[]) [GMS] NodeA-30899: JOIN(NodeA-30899) sent to NodeA-2608 timed out (after 2000 ms), on try 0 > 09:09:02,776 TRACE (testng:[]) [GMS] NodeA-30899: discovery took 0 ms, members: 21 rsps (5 coords) [done] > 09:09:02,776 DEBUG (testng:[]) [GMS] NodeA-30899: found multiple coords: [NodeA-2608, NodeA-5606, NodeA-17288, NodeA-64297, NodeA-48475] > 09:09:02,776 DEBUG (testng:[]) [GMS] NodeA-30899: sending JOIN(NodeA-30899) to NodeA-5606 > 09:09:04,776 WARN (testng:[]) [GMS] NodeA-30899: JOIN(NodeA-30899) sent to NodeA-5606 timed out (after 2000 ms), on try 1 > ... > 09:09:12,777 TRACE (testng:[]) [GMS] NodeA-30899: discovery took 0 ms, members: 21 rsps (5 coords) [done] > 09:09:12,778 DEBUG (testng:[]) [GMS] NodeA-30899: found multiple coords: [NodeA-2608, NodeA-5606, NodeA-17288, NodeA-64297, NodeA-48475] > 09:09:12,778 DEBUG (testng:[]) [GMS] NodeA-30899: sending JOIN(NodeA-30899) to NodeA-2608 > 09:09:14,778 WARN (testng:[]) [GMS] NodeA-30899: JOIN(NodeA-30899) sent to NodeA-2608 timed out (after 2000 ms), on try 2 > ... > 09:09:22,780 WARN (testng:[]) [GMS] NodeA-30899: too many JOIN attempts (3): becoming singleton > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11114) NonTxBackupOwnerBecomingPrimaryOwnerTest takes too long

by Dan Berindei (Jira)

[ https://issues.redhat.com/browse/ISPN-11114?page=com.atlassian.jira.plugi... ] Dan Berindei updated ISPN-11114: -------------------------------- Status: Open (was: New) > NonTxBackupOwnerBecomingPrimaryOwnerTest takes too long > ------------------------------------------------------- > > Key: ISPN-11114 > URL: https://issues.redhat.com/browse/ISPN-11114 > Project: Infinispan > Issue Type: Bug > Components: Core, Test Suite > Affects Versions: 10.1.0.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Minor > Fix For: 11.0.0.Final, 10.1.1.Final > > > {{NonTxBackupOwnerBecomingPrimaryOwnerTest}} installs a {{LocalTopologyManagerImpl}} to block topology updates, and never stops blocking. That makes cluster shutdown very slow, as each node leaving triggers a topology updates, and since ISPN-10310 the coordinator doesn't spawn a new thread for the topology update. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11114) NonTxBackupOwnerBecomingPrimaryOwnerTest takes too long

by Dan Berindei (Jira)

[ https://issues.redhat.com/browse/ISPN-11114?page=com.atlassian.jira.plugi... ] Dan Berindei updated ISPN-11114: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/7709 > NonTxBackupOwnerBecomingPrimaryOwnerTest takes too long > ------------------------------------------------------- > > Key: ISPN-11114 > URL: https://issues.redhat.com/browse/ISPN-11114 > Project: Infinispan > Issue Type: Bug > Components: Core, Test Suite > Affects Versions: 10.1.0.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Minor > Fix For: 11.0.0.Final, 10.1.1.Final > > > {{NonTxBackupOwnerBecomingPrimaryOwnerTest}} installs a {{LocalTopologyManagerImpl}} to block topology updates, and never stops blocking. That makes cluster shutdown very slow, as each node leaving triggers a topology updates, and since ISPN-10310 the coordinator doesn't spawn a new thread for the topology update. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11114) NonTxBackupOwnerBecomingPrimaryOwnerTest takes too long

by Dan Berindei (Jira)

Dan Berindei created ISPN-11114: ----------------------------------- Summary: NonTxBackupOwnerBecomingPrimaryOwnerTest takes too long Key: ISPN-11114 URL: https://issues.redhat.com/browse/ISPN-11114 Project: Infinispan Issue Type: Bug Components: Core, Test Suite Affects Versions: 10.1.0.Final Reporter: Dan Berindei Assignee: Dan Berindei Fix For: 11.0.0.Final, 10.1.1.Final {{NonTxBackupOwnerBecomingPrimaryOwnerTest}} installs a {{LocalTopologyManagerImpl}} to block topology updates, and never stops blocking. That makes cluster shutdown very slow, as each node leaving triggers a topology updates, and since ISPN-10310 the coordinator doesn't spawn a new thread for the topology update. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7623) Delta write during topology change broken with triangle

by Dan Berindei (Jira)

[ https://issues.redhat.com/browse/ISPN-7623?page=com.atlassian.jira.plugin... ] Dan Berindei resolved ISPN-7623. -------------------------------- Resolution: Out of Date Delta writes were removed with ISPN-10230 > Delta write during topology change broken with triangle > ------------------------------------------------------- > > Key: ISPN-7623 > URL: https://issues.redhat.com/browse/ISPN-7623 > Project: Infinispan > Issue Type: Bug > Components: Core > Reporter: Radim Vansa > Priority: Major > > Applying delta write on backup requires old value to be retrieved if it's not present (e.g. when a node has just become an owner). With old replication, the entry is not committed on primary owner until backup confirms the write, and therefore the backup can retrieve the old value. > With triangle, primary owner commits the value ~concurrently to sending the command to backup owner. Therefore, if backup asks for the value, it likely gets the updated value instead of the original. > This would affect any command with {{LoadType.OWNER}}, but currently triangle is not implemented by functional commands which have this load type. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11113) ScatteredDelayedAvailabilityUpdateTest takes too long

by Dan Berindei (Jira)

[ https://issues.redhat.com/browse/ISPN-11113?page=com.atlassian.jira.plugi... ] Dan Berindei updated ISPN-11113: -------------------------------- Priority: Minor (was: Major) > ScatteredDelayedAvailabilityUpdateTest takes too long > ----------------------------------------------------- > > Key: ISPN-11113 > URL: https://issues.redhat.com/browse/ISPN-11113 > Project: Infinispan > Issue Type: Bug > Components: Core, Test Suite > Affects Versions: 10.1.0.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Minor > Fix For: 11.0.0.Final, 10.1.1.Final > > > Partition handling tests use {{LOCAL_PING.setClusterName()}} with a unique name to disable discovery, otherwise partitions would try to merge while they are supposed to stay separate. > But {{LOCAL_PING}} uses the cluster name on stop to remove the node from the static discovery map. If the test doesn't change the cluster name back, {{LOCAL_PING}} doesn't remove the node, the next test method sees an existing coordinator, and tries to connect to it. When a test has lots of test methods, like {{ScatteredDelayedAvailabilityUpdateTest}}, each test method leaves one more coordinator in the discovery map, and each test method takes longer to start the first method. > {noformat} > 09:08:52,758 DEBUG (testng:[]) [GMS] address=NodeA-30899, cluster=org.infinispan.partitionhandling.ScatteredDelayedAvailabilityUpdateTest[SCATTERED_SYNC, bias=NEVER, DENY_READ_WRITES], physical address=127.0.0.1:51941 > 09:08:52,774 TRACE (testng:[]) [GMS] NodeA-30899: discovery took 0 ms, members: 21 rsps (5 coords) [done] > 09:08:52,774 DEBUG (testng:[]) [GMS] NodeA-30899: found multiple coords: [NodeA-2608, NodeA-5606, NodeA-17288, NodeA-64297, NodeA-48475] > 09:08:52,774 DEBUG (testng:[]) [GMS] NodeA-30899: sending JOIN(NodeA-30899) to NodeA-5606 > 09:08:54,774 WARN (testng:[]) [GMS] NodeA-30899: JOIN(NodeA-30899) sent to NodeA-5606 timed out (after 2000 ms), on try 0 > 09:08:54,774 DEBUG (testng:[]) [GMS] NodeA-30899: sending JOIN(NodeA-30899) to NodeA-64297 > 09:08:56,775 WARN (testng:[]) [GMS] NodeA-30899: JOIN(NodeA-30899) sent to NodeA-64297 timed out (after 2000 ms), on try 0 > 09:08:56,775 DEBUG (testng:[]) [GMS] NodeA-30899: sending JOIN(NodeA-30899) to NodeA-48475 > 09:08:58,775 WARN (testng:[]) [GMS] NodeA-30899: JOIN(NodeA-30899) sent to NodeA-48475 timed out (after 2000 ms), on try 0 > 09:08:58,775 DEBUG (testng:[]) [GMS] NodeA-30899: sending JOIN(NodeA-30899) to NodeA-17288 > 09:09:00,776 WARN (testng:[]) [GMS] NodeA-30899: JOIN(NodeA-30899) sent to NodeA-17288 timed out (after 2000 ms), on try 0 > 09:09:00,776 DEBUG (testng:[]) [GMS] NodeA-30899: sending JOIN(NodeA-30899) to NodeA-2608 > 09:09:02,776 WARN (testng:[]) [GMS] NodeA-30899: JOIN(NodeA-30899) sent to NodeA-2608 timed out (after 2000 ms), on try 0 > 09:09:02,776 TRACE (testng:[]) [GMS] NodeA-30899: discovery took 0 ms, members: 21 rsps (5 coords) [done] > 09:09:02,776 DEBUG (testng:[]) [GMS] NodeA-30899: found multiple coords: [NodeA-2608, NodeA-5606, NodeA-17288, NodeA-64297, NodeA-48475] > 09:09:02,776 DEBUG (testng:[]) [GMS] NodeA-30899: sending JOIN(NodeA-30899) to NodeA-5606 > 09:09:04,776 WARN (testng:[]) [GMS] NodeA-30899: JOIN(NodeA-30899) sent to NodeA-5606 timed out (after 2000 ms), on try 1 > ... > 09:09:12,777 TRACE (testng:[]) [GMS] NodeA-30899: discovery took 0 ms, members: 21 rsps (5 coords) [done] > 09:09:12,778 DEBUG (testng:[]) [GMS] NodeA-30899: found multiple coords: [NodeA-2608, NodeA-5606, NodeA-17288, NodeA-64297, NodeA-48475] > 09:09:12,778 DEBUG (testng:[]) [GMS] NodeA-30899: sending JOIN(NodeA-30899) to NodeA-2608 > 09:09:14,778 WARN (testng:[]) [GMS] NodeA-30899: JOIN(NodeA-30899) sent to NodeA-2608 timed out (after 2000 ms), on try 2 > ... > 09:09:22,780 WARN (testng:[]) [GMS] NodeA-30899: too many JOIN attempts (3): becoming singleton > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 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 December 2019