June 2020 - infinispan-issues - Jboss List Archives

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

by Nistor Adrian (Jira)

[ https://issues.redhat.com/browse/ISPN-9592?page=com.atlassian.jira.plugin... ] Nistor Adrian updated ISPN-9592: -------------------------------- Labels: SesarchNG (was: ) > Lockdown query internals > ------------------------ > > Key: ISPN-9592 > URL: https://issues.redhat.com/browse/ISPN-9592 > Project: Infinispan > Issue Type: Task > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Labels: SesarchNG > Fix For: 12.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)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10957) Index/Query by key

by Nistor Adrian (Jira)

[ https://issues.redhat.com/browse/ISPN-10957?page=com.atlassian.jira.plugi... ] Nistor Adrian updated ISPN-10957: --------------------------------- Labels: SearchNG (was: ) > Index/Query by key > ------------------ > > Key: ISPN-10957 > URL: https://issues.redhat.com/browse/ISPN-10957 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying > Reporter: Tristan Tarrant > Assignee: Nistor Adrian > Priority: Major > Labels: SearchNG > Fix For: 12.0.0.Final > > > We should offer the ability to query by key both in non-indexed mode as well as adding the key to the index using some special field name -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11187) Completely remove support for Index.LOCAL in parser and config

by Nistor Adrian (Jira)

[ https://issues.redhat.com/browse/ISPN-11187?page=com.atlassian.jira.plugi... ] Nistor Adrian updated ISPN-11187: --------------------------------- Labels: SearchNG (was: ) > Completely remove support for Index.LOCAL in parser and config > -------------------------------------------------------------- > > Key: ISPN-11187 > URL: https://issues.redhat.com/browse/ISPN-11187 > Project: Infinispan > Issue Type: Task > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Labels: SearchNG > Fix For: 12.0.0.Final > > > Support for Index.LOCAL has been removed already but in some places in code we still accept it leniently and convert it to Index.PRIMARY_OWNER and issue a warning in 10.x to ease config migration. In 11 we should completely remove that also. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11426) Add UUID to core SerializationContexts

by Nistor Adrian (Jira)

[ https://issues.redhat.com/browse/ISPN-11426?page=com.atlassian.jira.plugi... ] Nistor Adrian updated ISPN-11426: --------------------------------- Status: Open (was: New) > Add UUID to core SerializationContexts > -------------------------------------- > > Key: ISPN-11426 > URL: https://issues.redhat.com/browse/ISPN-11426 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Affects Versions: 10.1.3.Final, 11.0.0.Alpha2 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 12.0.0.Final > > > Currently we only register a ProtoStream marshaller for java.util.UUID in the server as they are required for the event logger, however this will also be required by core for `MultiClusterEventCommand` and `ClusterEvent`. It's not possible to register a class in multiple contexts when utilising a TypeId, therefore in order to avoid having to provide a TypeId for UUIDs in both core and server, we should register this in the core's persistence initializers. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11466) NettyTransportConnectionStats should not rely on the JMX support

by Nistor Adrian (Jira)

[ https://issues.redhat.com/browse/ISPN-11466?page=com.atlassian.jira.plugi... ] Nistor Adrian reassigned ISPN-11466: ------------------------------------ Assignee: Nistor Adrian > NettyTransportConnectionStats should not rely on the JMX support > ---------------------------------------------------------------- > > Key: ISPN-11466 > URL: https://issues.redhat.com/browse/ISPN-11466 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 10.1.0.Final > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 12.0.0.Final > > > Looking up those transports via jmx only works with jmx enabled. Should work regardless of that. > Keep in mind that these stats are exported as MP metrics. And jmx is not always available. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11797) Introduce strong typed indexing configuration

by Nistor Adrian (Jira)

[ https://issues.redhat.com/browse/ISPN-11797?page=com.atlassian.jira.plugi... ] Nistor Adrian updated ISPN-11797: --------------------------------- Labels: SearchNG (was: ) > Introduce strong typed indexing configuration > --------------------------------------------- > > Key: ISPN-11797 > URL: https://issues.redhat.com/browse/ISPN-11797 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying, Remote Querying > Affects Versions: 11.0.0.Dev05 > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Major > Labels: SearchNG > Fix For: 12.0.0.Final > > > {code:xml} >  > <indexing> > <indexed-entities> > <indexed-entity>org.infinispan.query.test.Person</indexed-entity> > </indexed-entities> > </indexing> > {code} > {code:xml} >  > <indexing storage="file" path="${server.data}/index"> > <indexed-entities> > <indexed-entity>org.infinispan.query.test.Person</indexed-entity> > </indexed-entities> > </indexing> > {code} > {code:xml} > <indexing storage="heap"> > <indexed-entities> > <indexed-entity>org.infinispan.query.test.Person</indexed-entity> > </indexed-entities> > </indexing> > {code} > {code:xml} >  > <indexing storage="file" path="${server.data}/index"> > <index-reader refresh-interval="10s"/> >  > <index-writer mode="async" commit-internal="10s"/> > <indexed-entities> > <indexed-entity>org.infinispan.query.test.Person</indexed-entity> > </indexed-entities> > <properties> > <property name="default.indexwriter.merge_factor">30</property> > </properties> > </indexing> > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11581) Query documentation is outdated

by Gustavo Fernandes (Jira)

[ https://issues.redhat.com/browse/ISPN-11581?page=com.atlassian.jira.plugi... ] Gustavo Fernandes closed ISPN-11581. ------------------------------------ Resolution: Out of Date > Query documentation is outdated > ------------------------------- > > Key: ISPN-11581 > URL: https://issues.redhat.com/browse/ISPN-11581 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation > Reporter: Gustavo Fernandes > Assignee: Donald Naro > Priority: Major > Fix For: 12.0.0.Final > > > It needs a full review since many things changed on 11.0, such as removal of InfinispanIndexManager, AffinityIndexManager, auto-broadcast, removal of Index.ALL/NONE/PRIMARY_OWNER, hibernate search upgrade, etc -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5557) Core threading redesign

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-5557?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-5557: ---------------------------------- Fix Version/s: 12.0.0.Final (was: 11.0.0.Final) > Core threading redesign > ----------------------- > > Key: ISPN-5557 > URL: https://issues.redhat.com/browse/ISPN-5557 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 7.2.2.Final > Reporter: Dan Berindei > Assignee: Will Burns > Priority: Critical > Fix For: 12.0.0.Final > > > Infinispan needs a lot of threads, because everything is synchronous: locking, remote command invocations, cache writers. This causes various issues, from general context switching overhead to the thread pools getting full and causing deadlocks. > We should redesign the core so that most blocking happens on the application threads, and the number of internal threads is kept to a minimum. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5938) ClusterListenerReplInitialStateTest.testPrimaryOwnerGoesDownAfterBackupRaisesEvent fails randomly

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-5938?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-5938: ---------------------------------- Fix Version/s: 12.0.0.Final (was: 11.0.0.Final) > ClusterListenerReplInitialStateTest.testPrimaryOwnerGoesDownAfterBackupRaisesEvent fails randomly > ------------------------------------------------------------------------------------------------- > > Key: ISPN-5938 > URL: https://issues.redhat.com/browse/ISPN-5938 > Project: Infinispan > Issue Type: Bug > Components: Test Suite > Affects Versions: 11.0.0.Alpha1 > Reporter: Roman Macor > Assignee: Dan Berindei > Priority: Major > Fix For: 12.0.0.Final > > > ClusterListenerReplInitialStateTest.testPrimaryOwnerGoesDownAfterBackupRaisesEvent fails randomly with: > Stacktrace > java.util.concurrent.TimeoutException > at java.util.concurrent.FutureTask.get(FutureTask.java:205) > at org.infinispan.notifications.cachelistener.cluster.ClusterListenerReplTest.testPrimaryOwnerGoesDownAfterBackupRaisesEvent(ClusterListenerReplTest.java:123) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80) > at org.testng.internal.Invoker.invokeMethod(Invoker.java:714) > at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901) > at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231) > at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127) > at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111) > at org.testng.TestRunner.privateRun(TestRunner.java:767) > at org.testng.TestRunner.run(TestRunner.java:617) > at org.testng.SuiteRunner.runTest(SuiteRunner.java:334) > at org.testng.SuiteRunner.access$000(SuiteRunner.java:37) > at org.testng.SuiteRunner$SuiteWorker.run(SuiteRunner.java:368) > at org.testng.internal.thread.ThreadUtil$2.call(ThreadUtil.java:64) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10309) Convert Remaining Parts to Non Blocking & Reduce Thread Pools

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-10309?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-10309: ----------------------------------- Fix Version/s: 12.0.0.Final (was: 11.0.0.Final) > Convert Remaining Parts to Non Blocking & Reduce Thread Pools > ------------------------------------------------------------- > > Key: ISPN-10309 > URL: https://issues.redhat.com/browse/ISPN-10309 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 12.0.0.Final > > > We would love to get our thread pools down to a single CPU thread pool (size = numCores) and a blocking thread pool (arbitrarily large). We may also require a scheduler pool for various options as well (limited size 1-2?). > To do this we need to remove remnants of our blocking code as possible. Possible issues for blocking are mostly around locks and io operations. > The persistence layer was completed with ISPN-9722 so that is not an issue. > The requirement around locking can be relaxed if the locks are guaranteed to be small in scope and do not wrap other blocking operations. An example would be a lock such as ones in CHM as long as we don't have large blocks for functional argument types. > If code cannot be made non blocking we must offload the operation to the blocking thread pool. Care must be taken to ensure that once the blocking portion of code is completed that we switch back the to CPU thread pool as soon as possible. The listener API for example is violating this and will run code in Infinispan from any thread that completes the listener that could be done from a user. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 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 June 2020