June 2014 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-3808) Performance assesment of the Remote Query functionality

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-3808?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-3808: ---------------------------------- Labels: 6.3remotequeries 64QueryBlockers (was: 6.3remotequeries) > Performance assesment of the Remote Query functionality > ------------------------------------------------------- > > Key: ISPN-3808 > URL: https://issues.jboss.org/browse/ISPN-3808 > Project: Infinispan > Issue Type: Task > Components: Embedded Querying > Reporter: Sanne Grinovero > Assignee: Adrian Nistor > Labels: 6.3remotequeries, 64QueryBlockers > -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3835) Index Update command is processed before the registry listener is triggered

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-3835?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-3835: ---------------------------------- Labels: 64QueryBlockers (was: ) > Index Update command is processed before the registry listener is triggered > --------------------------------------------------------------------------- > > Key: ISPN-3835 > URL: https://issues.jboss.org/browse/ISPN-3835 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Affects Versions: 6.0.0.Final > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Priority: Critical > Labels: 64QueryBlockers > Fix For: 7.0.0.Beta1 > > > When using the InfinispanIndexManager backend the master node might receive an index update command about an index which it hasn't defined yet. > Index definitions are triggered by the type registry, which in turn is driven by the ClusterRegistry and an event listener on the ClusterRegistry. It looks like slaves are sending update requests before the master has processed the configuration event. > This leads to index update commands to be lost (with a stacktrace logged) -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3949) Support querying on simple values

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-3949?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-3949: ---------------------------------- Labels: 64QueryBlockers (was: ) > Support querying on simple values > --------------------------------- > > Key: ISPN-3949 > URL: https://issues.jboss.org/browse/ISPN-3949 > Project: Infinispan > Issue Type: Feature Request > Components: Embedded Querying > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Labels: 64QueryBlockers > Fix For: 7.0.0.Final > > > Ironically while we support searching on rich domain objects, we don't allow running queries on the most simple types which users could store in the grid: Strings, Numbers. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3983) Remove some performance bottlenecks from ProtoStream

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-3983?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-3983: ---------------------------------- Labels: 6.3remotequeries 630 64QueryBlockers (was: 6.3remotequeries 630) > Remove some performance bottlenecks from ProtoStream > ---------------------------------------------------- > > Key: ISPN-3983 > URL: https://issues.jboss.org/browse/ISPN-3983 > Project: Infinispan > Issue Type: Bug > Components: Remote Querying > Affects Versions: 6.0.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Labels: 6.3remotequeries, 630, 64QueryBlockers > Fix For: 7.0.0.Beta1, 7.0.0.Final > > > Profiling has shown that there are many HashMaps created in MessageContext to help field lookup by name. > Normally this is a static piece of information that should be computed only once when a marshaller is registered and then it should become immutable and be reused. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4004) Validate performance of queries over Hot rod

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-4004?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-4004: ---------------------------------- Labels: 64QueryBlockers (was: ) > Validate performance of queries over Hot rod > -------------------------------------------- > > Key: ISPN-4004 > URL: https://issues.jboss.org/browse/ISPN-4004 > Project: Infinispan > Issue Type: Enhancement > Components: Remote Querying > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Priority: Critical > Labels: 64QueryBlockers > Fix For: 7.0.0.Final > > -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4088) Modify signature of Query/CacheQuery.getResultSize() and related offset/pagination methods to return long

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-4088?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-4088: ---------------------------------- Labels: 64QueryBlockers (was: ) > Modify signature of Query/CacheQuery.getResultSize() and related offset/pagination methods to return long > --------------------------------------------------------------------------------------------------------- > > Key: ISPN-4088 > URL: https://issues.jboss.org/browse/ISPN-4088 > Project: Infinispan > Issue Type: Feature Request > Components: Embedded Querying, Remote Querying > Affects Versions: 6.0.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Labels: 64QueryBlockers > Fix For: 7.0.0.Final > > > The method exists in both new DSL and the classic query api. > It should be clarified whether this method and the related pagination methods should use int or long for specifying offsets within the data, also should decide if the total number of results / results per page is a long or an int - and update all involved method signatures to have a unitary treatment of this issue. > It appears that recent Lucene versions can offer the number of results as long, while older ones offer it as int (should be verified). > This issue was raised in a github conversation here: https://github.com/infinispan/infinispan/pull/2410 -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4175) Initialisation of remote query module fails randomly due to ClusterRegistry not bein initialised

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-4175?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-4175: ---------------------------------- Labels: 64QueryBlockers (was: ) > Initialisation of remote query module fails randomly due to ClusterRegistry not bein initialised > ------------------------------------------------------------------------------------------------ > > Key: ISPN-4175 > URL: https://issues.jboss.org/browse/ISPN-4175 > Project: Infinispan > Issue Type: Bug > Components: Remote Querying > Affects Versions: 6.0.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Labels: 64QueryBlockers > Fix For: 7.0.0.Final > > > {code} > 11:47:01,852 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.infinispan.clustered.memcachedCache: org.jboss.msc.service.StartException in service jboss.infinispan.clustered.memcachedCache: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_40] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_40] > at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_40] > Caused by: org.infinispan.manager.EmbeddedCacheManagerStartupException: org.infinispan.commons.CacheConfigurationException: No registered default factory for component 'interface org.infinispan.registry.ClusterRegistry' found!. To get more detail set the system property infinispan.debugDependencies to true > at org.infinispan.factories.GlobalComponentRegistry.start(GlobalComponentRegistry.java:241) > at org.infinispan.manager.DefaultCacheManager.wireAndStartCache(DefaultCacheManager.java:546) > at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:517) > at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:399) > at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:413) > at org.jboss.as.clustering.infinispan.DefaultEmbeddedCacheManager.getCache(DefaultEmbeddedCacheManager.java:89) > at org.jboss.as.clustering.infinispan.DefaultEmbeddedCacheManager.getCache(DefaultEmbeddedCacheManager.java:80) > at org.jboss.as.clustering.infinispan.subsystem.CacheService.start(CacheService.java:78) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1] > ... 3 more > Caused by: org.infinispan.commons.CacheConfigurationException: No registered default factory for component 'interface org.infinispan.registry.ClusterRegistry' found!. To get more detail set the system property infinispan.debugDependencies to true > at org.infinispan.factories.AbstractComponentRegistry.throwStackAwareConfigurationException(AbstractComponentRegistry.java:884) > at org.infinispan.factories.AbstractComponentRegistry.getFactory(AbstractComponentRegistry.java:299) > at org.infinispan.factories.AbstractComponentRegistry.getOrCreateComponent(AbstractComponentRegistry.java:270) > at org.infinispan.factories.AbstractComponentRegistry.invokeInjectionMethod(AbstractComponentRegistry.java:227) > at org.infinispan.factories.AbstractComponentRegistry.access$000(AbstractComponentRegistry.java:65) > at org.infinispan.factories.AbstractComponentRegistry$Component.injectDependencies(AbstractComponentRegistry.java:797) > at org.infinispan.factories.AbstractComponentRegistry.registerComponentInternal(AbstractComponentRegistry.java:201) > at org.infinispan.factories.AbstractComponentRegistry.registerComponent(AbstractComponentRegistry.java:156) > at org.infinispan.factories.AbstractComponentRegistry.registerComponent(AbstractComponentRegistry.java:148) > at org.infinispan.query.remote.LifecycleManager.initProtobufMetadataManager(LifecycleManager.java:56) > at org.infinispan.query.remote.LifecycleManager.cacheManagerStarted(LifecycleManager.java:70) > at org.infinispan.factories.GlobalComponentRegistry.start(GlobalComponentRegistry.java:228) > ... 12 more > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4065) Refuse to store an index on an ASYNC Cache

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-4065?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-4065: ---------------------------------- Labels: 64QueryBlockers (was: ) > Refuse to store an index on an ASYNC Cache > ------------------------------------------ > > Key: ISPN-4065 > URL: https://issues.jboss.org/browse/ISPN-4065 > Project: Infinispan > Issue Type: Enhancement > Components: Lucene Directory > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Priority: Minor > Labels: 64QueryBlockers > Fix For: 7.0.0.Beta1, 7.0.0.Final > > -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4226) SearchManagerImpl use a bad entity names resolver

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-4226?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-4226: ---------------------------------- Labels: 64QueryBlockers (was: ) > SearchManagerImpl use a bad entity names resolver > ------------------------------------------------- > > Key: ISPN-4226 > URL: https://issues.jboss.org/browse/ISPN-4226 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying > Affects Versions: 6.0.2.Final > Environment: Wildfly 8.1.0 CR1 > Reporter: David Cabillic > Assignee: Sanne Grinovero > Labels: 64QueryBlockers > Fix For: 7.0.0.Beta1 > > > Inner class org.infinispan.query.impl.SearchManagerImpl$EntityNamesResolver used in method SearchManagerImpl#getQueryFactory use Class.forName(String) instead of Thread.currentThread().getContextClassLoader().loadClass(String) > It is a problem if @Indexed classes are in an EAR/WAR which is not loaded in the same ClassLoader. It works great with ContextClassLoader. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4226) SearchManagerImpl use a bad entity names resolver

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-4226?page=com.atlassian.jira.plugin.... ] Sanne Grinovero reassigned ISPN-4226: ------------------------------------- Assignee: Sanne Grinovero (was: Adrian Nistor) > SearchManagerImpl use a bad entity names resolver > ------------------------------------------------- > > Key: ISPN-4226 > URL: https://issues.jboss.org/browse/ISPN-4226 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying > Affects Versions: 6.0.2.Final > Environment: Wildfly 8.1.0 CR1 > Reporter: David Cabillic > Assignee: Sanne Grinovero > Fix For: 7.0.0.Beta1 > > > Inner class org.infinispan.query.impl.SearchManagerImpl$EntityNamesResolver used in method SearchManagerImpl#getQueryFactory use Class.forName(String) instead of Thread.currentThread().getContextClassLoader().loadClass(String) > It is a problem if @Indexed classes are in an EAR/WAR which is not loaded in the same ClassLoader. It works great with ContextClassLoader. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 4 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 2014