October 2019 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-9592) Lockdown query internals

by Pedro Zapata Fernandez (Jira)

[ https://issues.jboss.org/browse/ISPN-9592?page=com.atlassian.jira.plugin.... ] Pedro Zapata Fernandez updated ISPN-9592: ----------------------------------------- Sprint: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34 (was: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35) > Lockdown query internals > ------------------------ > > Key: ISPN-9592 > URL: https://issues.jboss.org/browse/ISPN-9592 > Project: Infinispan > Issue Type: Task > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 11.0.0.Final > > > Many things in query implementation are left public although they are very prone to creating insidious bugs if accessed externally. These are not proper extension points and should be made package local or provided strictly via SearchManagerImplementor. > * Move SearchManager.purge(Class) method to SearchManagerImplementor > * DefaultSearchWorkCreator should be moved to org.infinispan.query.backend and made package local > * TransactionalEventTransactionContext is not used, can be removed, and its non-tx counterpart (NoTransactionContext) no longer has to be public > * all public methods in QueryInterceptor must be reviewed and made package local ASAP -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

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

by Pedro Zapata Fernandez (Jira)

[ https://issues.jboss.org/browse/ISPN-2575?page=com.atlassian.jira.plugin.... ] Pedro Zapata Fernandez updated ISPN-2575: ----------------------------------------- Sprint: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 9.4.0.Final, Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34 (was: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 9.4.0.Final, Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35) > Key Transformer 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: Embedded Querying > Affects Versions: 5.2.0.Beta5 > Reporter: Anna Manukyan > Assignee: Nistor Adrian > Priority: Minor > Fix For: 10.0.0.Final > > 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 was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9322) Remove all usages of @IndexedField protostream annotation

by Pedro Zapata Fernandez (Jira)

[ https://issues.jboss.org/browse/ISPN-9322?page=com.atlassian.jira.plugin.... ] Pedro Zapata Fernandez updated ISPN-9322: ----------------------------------------- Fix Version/s: 11.0.0.Final (was: 10.0.0.Final) > Remove all usages of @IndexedField protostream annotation > --------------------------------------------------------- > > Key: ISPN-9322 > URL: https://issues.jboss.org/browse/ISPN-9322 > Project: Infinispan > Issue Type: Bug > Components: Remote Querying > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Labels: SearchNG > Fix For: 11.0.0.Final > > > This annotation is deprecated and should be replaced with @Field but we still have several usages in our test suite. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9156) Protobuf metadata cache should not have invocation batching enabled

by Pedro Zapata Fernandez (Jira)

[ https://issues.jboss.org/browse/ISPN-9156?page=com.atlassian.jira.plugin.... ] Pedro Zapata Fernandez updated ISPN-9156: ----------------------------------------- Sprint: DataGrid Sprint #34 (was: DataGrid Sprint #34, DataGrid Sprint #35) > Protobuf metadata cache should not have invocation batching enabled > ------------------------------------------------------------------- > > Key: ISPN-9156 > URL: https://issues.jboss.org/browse/ISPN-9156 > Project: Infinispan > Issue Type: Enhancement > Components: Remote Querying > Reporter: Galder Zamarreño > Assignee: Nistor Adrian > Priority: Major > Labels: redhat-summit-18 > Fix For: 10.0.0.Final > > > As a result of having invocation batching enabled, any update failures would not make the cache operations fail. > Although surprising, that's an expected behaviour of invocation batching. It should be better documented (see [discussion email|https://markmail.org/message/gbvtv6a3w4gtsvj6]). -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9498) Index filesystem paths in server should point to data directory

by Pedro Zapata Fernandez (Jira)

[ https://issues.jboss.org/browse/ISPN-9498?page=com.atlassian.jira.plugin.... ] Pedro Zapata Fernandez reassigned ISPN-9498: -------------------------------------------- Assignee: Tristan Tarrant (was: Gustavo Fernandes) > Index filesystem paths in server should point to data directory > --------------------------------------------------------------- > > Key: ISPN-9498 > URL: https://issues.jboss.org/browse/ISPN-9498 > Project: Infinispan > Issue Type: Bug > Components: Indexing, OpenShift, Server > Affects Versions: 9.4.0.CR1, 9.3.3.Final > Reporter: Galder Zamarreño > Assignee: Tristan Tarrant > Priority: Major > > Certain indexing configurations result in using filesystem as index storage. > When running such configurations in a server environment, filesystem path should be somewhere within the server's data directory. This is the natural place for such data. > When running in OpenShift, server's data folder can be backed by a persistent volume. This means that the fileystem volume survives after restarts. > Plugging server's data directory is already happening for [file-store|https://github.com/infinispan/infinispan/blob/master/server/in...] and [rocksdb-store|https://github.com/infinispan/infinispan/blob/master/server...]. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10546) Introduce parent configuration element

by Pedro Zapata Fernandez (Jira)

[ https://issues.jboss.org/browse/ISPN-10546?page=com.atlassian.jira.plugin... ] Pedro Zapata Fernandez updated ISPN-10546: ------------------------------------------ Sprint: DataGrid Sprint #34 (was: DataGrid Sprint #34, DataGrid Sprint #35) > Introduce parent configuration element > -------------------------------------- > > Key: ISPN-10546 > URL: https://issues.jboss.org/browse/ISPN-10546 > Project: Infinispan > Issue Type: Enhancement > Components: Configuration, Core > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Major > > Introduce a class InfinispanConfiguration that will contain the GlobalConfiguration, ThreadConfiguration and JGroupsConfiguration, to align with the XML schema other elements are managed outside the <cache-container> -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9555) ComponentRegistry should enforce that registered components implement the interface/contract

by Pedro Zapata Fernandez (Jira)

[ https://issues.jboss.org/browse/ISPN-9555?page=com.atlassian.jira.plugin.... ] Pedro Zapata Fernandez updated ISPN-9555: ----------------------------------------- Sprint: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 9.4.0.Final, Sprint 10.0.0.Alpha0, Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34 (was: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 9.4.0.Final, Sprint 10.0.0.Alpha0, Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35) > ComponentRegistry should enforce that registered components implement the interface/contract > -------------------------------------------------------------------------------------------- > > Key: ISPN-9555 > URL: https://issues.jboss.org/browse/ISPN-9555 > Project: Infinispan > Issue Type: Bug > Components: Core > Reporter: Nistor Adrian > Assignee: Dan Berindei > Priority: Major > Fix For: 10.0.0.Final > > > ComponentRegistry.registerComponent(impl, interface) does not currently check that the impl really is assignable to the interface. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9270) ClusteredLockWith2NodesTest.testTryLockAndKillLocking random failures

by Pedro Zapata Fernandez (Jira)

[ https://issues.jboss.org/browse/ISPN-9270?page=com.atlassian.jira.plugin.... ] Pedro Zapata Fernandez updated ISPN-9270: ----------------------------------------- Sprint: Sprint 9.3.0.Final, Sprint 9.4.0.Beta1, Sprint 9.4.0.CR1, Sprint 9.4.0.CR3, Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 9.4.0.Final, Sprint 10.0.0.Alpha0, Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34 (was: Sprint 9.3.0.Final, Sprint 9.4.0.Beta1, Sprint 9.4.0.CR1, Sprint 9.4.0.CR3, Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 9.4.0.Final, Sprint 10.0.0.Alpha0, Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35) > ClusteredLockWith2NodesTest.testTryLockAndKillLocking random failures > --------------------------------------------------------------------- > > Key: ISPN-9270 > URL: https://issues.jboss.org/browse/ISPN-9270 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 9.3.0.CR1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Labels: testsuite_stability > > The test stops the coordinator A of a 2-node cluster \[A, B\], and then verifies that B stays available. > Unfortunately that doesn't always happen: A tries to install topology \[B\] before shutting down, but B might receive it too late and reject it. If B expects members \[A, B\] and sees only B, the cache will enter degraded mode: > {noformat} > 19:04:05,863 INFO (jgroups-8,Test-NodeB-21374:[org.infinispan.LOCKS]) [CLUSTER] [Context=org.infinispan.LOCKS] ISPN100008: Updating cache members list [Test-NodeD-51051], topology id 7 > 19:04:05,863 TRACE (jgroups-4,Test-NodeD-51051:[]) [JGroupsTransport] Test-NodeD-51051 received command from Test-NodeB-21374: CacheTopologyControlCommand{cache=org.infinispan.LOCKS, type=CH_UPDATE, sender=Test-NodeB-21374, joinInfo=null, topologyId=7, rebalanceId=2, currentCH=ReplicatedConsistentHash{ns = 256, owners = (1)[Test-NodeD-51051: 256]}, pendingCH=null, availabilityMode=AVAILABLE, phase=NO_REBALANCE, actualMembers=[Test-NodeD-51051], throwable=null, viewId=1} > 19:04:05,880 INFO (jgroups-4,Test-NodeD-51051:[]) [CLUSTER] ISPN000094: Received new cluster view for channel ISPN: [Test-NodeD-51051|2] (1) [Test-NodeD-51051] > 19:04:05,884 DEBUG (stateTransferExecutor-thread-Test-NodeD-p101-t1:[Merge-2]) [ClusterCacheStatus] Recovered 1 partition(s) for cache org.infinispan.LOCKS: [CacheTopology{id=6, phase=NO_REBALANCE, rebalanceId=2, currentCH=ReplicatedConsistentHash{ns = 256, owners = (2)[Test-NodeB-21374: 124, Test-NodeD-51051: 132]}, pendingCH=null, unionCH=null, actualMembers=[Test-NodeD-51051], persistentUUIDs=[6ac3a341-5af4-4aa2-ae7b-a4183d02d959]}] > 19:04:05,884 WARN (stateTransferExecutor-thread-Test-NodeD-p101-t1:[Merge-2]) [CLUSTER] [Context=org.infinispan.LOCKS] ISPN000320: After merge (or coordinator change), cache still hasn't recovered a majority of members and must stay in degraded mode. Current members are [Test-NodeD-51051], lost members are [Test-NodeB-21374], stable members are [Test-NodeB-21374, Test-NodeD-51051] > 19:04:05,885 INFO (stateTransferExecutor-thread-Test-NodeD-p101-t1:[Merge-2]) [CLUSTER] [Context=org.infinispan.LOCKS] ISPN100011: Entering availability mode DEGRADED_MODE, topology id 8 > 19:04:05,941 DEBUG (transport-thread-Test-NodeD-p100-t2:[Topology-org.infinispan.LOCKS]) [LocalTopologyManagerImpl] Ignoring topology 7 for cache org.infinispan.LOCKS from old coordinator Test-NodeB-21374 > 19:04:06,024 ERROR (testng-Test:[]) [TestSuiteProgress] Test failed: org.infinispan.lock.ClusteredLockWith2NodesTest.testTryLockAndKillLocking > java.lang.Error: java.util.concurrent.ExecutionException: java.lang.Error: java.util.concurrent.ExecutionException: org.infinispan.lock.exception.ClusteredLockException: org.infinispan.partitionhandling.AvailabilityException: ISPN000306: Key 'ClusteredLockKey{name=Test}' is not available. Not all owners are in this partition > at org.infinispan.functional.FunctionalTestUtils.await(FunctionalTestUtils.java:47) ~[infinispan-core-9.3.0-SNAPSHOT-tests.jar:9.3.0-SNAPSHOT] > at org.infinispan.lock.ClusteredLockWith2NodesTest.testTryLockAndKillLocking(ClusteredLockWith2NodesTest.java:49) ~[test-classes/:?] > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9555) ComponentRegistry should enforce that registered components implement the interface/contract

by Pedro Zapata Fernandez (Jira)

[ https://issues.jboss.org/browse/ISPN-9555?page=com.atlassian.jira.plugin.... ] Pedro Zapata Fernandez closed ISPN-9555. ---------------------------------------- Resolution: Out of Date > ComponentRegistry should enforce that registered components implement the interface/contract > -------------------------------------------------------------------------------------------- > > Key: ISPN-9555 > URL: https://issues.jboss.org/browse/ISPN-9555 > Project: Infinispan > Issue Type: Bug > Components: Core > Reporter: Nistor Adrian > Assignee: Dan Berindei > Priority: Major > Fix For: 10.0.0.Final > > > ComponentRegistry.registerComponent(impl, interface) does not currently check that the impl really is assignable to the interface. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9270) ClusteredLockWith2NodesTest.testTryLockAndKillLocking random failures

by Pedro Zapata Fernandez (Jira)

[ https://issues.jboss.org/browse/ISPN-9270?page=com.atlassian.jira.plugin.... ] Pedro Zapata Fernandez updated ISPN-9270: ----------------------------------------- Fix Version/s: (was: 10.0.0.Final) > ClusteredLockWith2NodesTest.testTryLockAndKillLocking random failures > --------------------------------------------------------------------- > > Key: ISPN-9270 > URL: https://issues.jboss.org/browse/ISPN-9270 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 9.3.0.CR1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Labels: testsuite_stability > > The test stops the coordinator A of a 2-node cluster \[A, B\], and then verifies that B stays available. > Unfortunately that doesn't always happen: A tries to install topology \[B\] before shutting down, but B might receive it too late and reject it. If B expects members \[A, B\] and sees only B, the cache will enter degraded mode: > {noformat} > 19:04:05,863 INFO (jgroups-8,Test-NodeB-21374:[org.infinispan.LOCKS]) [CLUSTER] [Context=org.infinispan.LOCKS] ISPN100008: Updating cache members list [Test-NodeD-51051], topology id 7 > 19:04:05,863 TRACE (jgroups-4,Test-NodeD-51051:[]) [JGroupsTransport] Test-NodeD-51051 received command from Test-NodeB-21374: CacheTopologyControlCommand{cache=org.infinispan.LOCKS, type=CH_UPDATE, sender=Test-NodeB-21374, joinInfo=null, topologyId=7, rebalanceId=2, currentCH=ReplicatedConsistentHash{ns = 256, owners = (1)[Test-NodeD-51051: 256]}, pendingCH=null, availabilityMode=AVAILABLE, phase=NO_REBALANCE, actualMembers=[Test-NodeD-51051], throwable=null, viewId=1} > 19:04:05,880 INFO (jgroups-4,Test-NodeD-51051:[]) [CLUSTER] ISPN000094: Received new cluster view for channel ISPN: [Test-NodeD-51051|2] (1) [Test-NodeD-51051] > 19:04:05,884 DEBUG (stateTransferExecutor-thread-Test-NodeD-p101-t1:[Merge-2]) [ClusterCacheStatus] Recovered 1 partition(s) for cache org.infinispan.LOCKS: [CacheTopology{id=6, phase=NO_REBALANCE, rebalanceId=2, currentCH=ReplicatedConsistentHash{ns = 256, owners = (2)[Test-NodeB-21374: 124, Test-NodeD-51051: 132]}, pendingCH=null, unionCH=null, actualMembers=[Test-NodeD-51051], persistentUUIDs=[6ac3a341-5af4-4aa2-ae7b-a4183d02d959]}] > 19:04:05,884 WARN (stateTransferExecutor-thread-Test-NodeD-p101-t1:[Merge-2]) [CLUSTER] [Context=org.infinispan.LOCKS] ISPN000320: After merge (or coordinator change), cache still hasn't recovered a majority of members and must stay in degraded mode. Current members are [Test-NodeD-51051], lost members are [Test-NodeB-21374], stable members are [Test-NodeB-21374, Test-NodeD-51051] > 19:04:05,885 INFO (stateTransferExecutor-thread-Test-NodeD-p101-t1:[Merge-2]) [CLUSTER] [Context=org.infinispan.LOCKS] ISPN100011: Entering availability mode DEGRADED_MODE, topology id 8 > 19:04:05,941 DEBUG (transport-thread-Test-NodeD-p100-t2:[Topology-org.infinispan.LOCKS]) [LocalTopologyManagerImpl] Ignoring topology 7 for cache org.infinispan.LOCKS from old coordinator Test-NodeB-21374 > 19:04:06,024 ERROR (testng-Test:[]) [TestSuiteProgress] Test failed: org.infinispan.lock.ClusteredLockWith2NodesTest.testTryLockAndKillLocking > java.lang.Error: java.util.concurrent.ExecutionException: java.lang.Error: java.util.concurrent.ExecutionException: org.infinispan.lock.exception.ClusteredLockException: org.infinispan.partitionhandling.AvailabilityException: ISPN000306: Key 'ClusteredLockKey{name=Test}' is not available. Not all owners are in this partition > at org.infinispan.functional.FunctionalTestUtils.await(FunctionalTestUtils.java:47) ~[infinispan-core-9.3.0-SNAPSHOT-tests.jar:9.3.0-SNAPSHOT] > at org.infinispan.lock.ClusteredLockWith2NodesTest.testTryLockAndKillLocking(ClusteredLockWith2NodesTest.java:49) ~[test-classes/:?] > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 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 October 2019