December 2013 - infinispan-issues

[JBoss JIRA] (ISPN-3833) QueryInterceptor#updateKnownTypesIfNeeded invokes into the cluster registry too frequently

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-3833?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-3833: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/2286 > QueryInterceptor#updateKnownTypesIfNeeded invokes into the cluster registry too frequently > ------------------------------------------------------------------------------------------ > > Key: ISPN-3833 > URL: https://issues.jboss.org/browse/ISPN-3833 > Project: Infinispan > Issue Type: Enhancement > Components: Querying > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Fix For: 6.1.0.Final > > > The QueryInterceptor should use a local cache to avoid unnecessary invocations, especially as the cluster registry is transactional this is a source of garbage generation. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-3834) New advanced indexing flag to skip deletion of previous entry

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-3834?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-3834: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/2286 > New advanced indexing flag to skip deletion of previous entry > ------------------------------------------------------------- > > Key: ISPN-3834 > URL: https://issues.jboss.org/browse/ISPN-3834 > Project: Infinispan > Issue Type: Enhancement > Components: Querying > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Fix For: 6.1.0.Final > > > I'm needing to add a org.infinispan.context.Flag.SKIP_INDEX_CLEANUP which does not issue an UPDATE index command but a simple ADD. > Just ADD is way more efficient, just we can't automatically detect it safely so I need a flag to allow for efficient data import. -- 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

11 years

1
0
0 / 0

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

by Sanne Grinovero (JIRA)

Sanne Grinovero created ISPN-3835: ------------------------------------- Summary: 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: Querying Affects Versions: 6.0.0.Final Reporter: Sanne Grinovero Assignee: Sanne Grinovero Priority: Critical Fix For: 6.1.0.Final 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 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

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-3834) New advanced indexing flag to skip deletion of previous entry

by Sanne Grinovero (JIRA)

Sanne Grinovero created ISPN-3834: ------------------------------------- Summary: New advanced indexing flag to skip deletion of previous entry Key: ISPN-3834 URL: https://issues.jboss.org/browse/ISPN-3834 Project: Infinispan Issue Type: Enhancement Components: Querying Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: 6.1.0.Final I'm needing to add a org.infinispan.context.Flag.SKIP_INDEX_CLEANUP which does not issue an UPDATE index command but a simple ADD. Just ADD is way more efficient, just we can't automatically detect it safely so I need a flag to allow for efficient data import. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-3586) Improve performance of Infinispan Lucene directory provider

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-3586?page=com.atlassian.jira.plugin.... ] Sanne Grinovero commented on ISPN-3586: --------------------------------------- I have this now down to approx. 500 milliseconds (for 2000 entries), but using some tricks and some patches: - use batching - a little tuning of the indexing options - ISPN-3834 is drafted in this measurement > Improve performance of Infinispan Lucene directory provider > ----------------------------------------------------------- > > Key: ISPN-3586 > URL: https://issues.jboss.org/browse/ISPN-3586 > Project: Infinispan > Issue Type: Enhancement > Components: Lucene Directory > Affects Versions: 6.0.0.Beta2 > Reporter: Adrian Nistor > Assignee: Sanne Grinovero > > Currently in distributed mode it takes about 2 minutes to index 2000 entries. This was found in ISPN-3102. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-1599) Split entry locking in Data Lock(s) and Structure Lock(s)

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-1599?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-1599: ---------------------------------- Assignee: Dan Berindei (was: Manik Surtani) > Split entry locking in Data Lock(s) and Structure Lock(s) > --------------------------------------------------------- > > Key: ISPN-1599 > URL: https://issues.jboss.org/browse/ISPN-1599 > Project: Infinispan > Issue Type: Enhancement > Reporter: Sanne Grinovero > Assignee: Dan Berindei > > See mailing list thread: > http://lists.jboss.org/pipermail/infinispan-dev/2011-December/009605.html > http://infinispan.markmail.org/thread/k7sucf5dnuenuuf7 -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-1764) Remove threadLocal in org.infinispan.context.AbstractInvocationContextContainer

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-1764?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-1764: ---------------------------------- Assignee: Dan Berindei (was: Manik Surtani) > Remove threadLocal in org.infinispan.context.AbstractInvocationContextContainer > ------------------------------------------------------------------------------- > > Key: ISPN-1764 > URL: https://issues.jboss.org/browse/ISPN-1764 > Project: Infinispan > Issue Type: Enhancement > Reporter: Sanne Grinovero > Assignee: Dan Berindei > > The javadocs in org.infinispan.context.AbstractInvocationContextContainer mention: > {quote}// See ISPN-1397. There is no real need to store the InvocationContext in a thread local at all, since it is passed > // as a parameter to any component that requires it - except for two components at the moment that require reading > // the InvocationContext from a thread local. These two are the ClusterCacheLoader and the JBossMarshaller. The > // former can be fixed once the CacheStore SPI is changed to accept an InvocationContext (see ISPN-1416) and the > // latter can be fixed once the CacheManager architecture is changed to be associated with a ClassLoader per > // CacheManager (see ISPN-1413), after which this thread local can be removed and the getInvocationContext() method > // can also be removed. > {quote} -- 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

11 years

1
0
0 / 0

[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: ---------------------------------- Assignee: Adrian Nistor (was: Sanne Grinovero) > Performance assesment of the Remote Query functionality > ------------------------------------------------------- > > Key: ISPN-3808 > URL: https://issues.jboss.org/browse/ISPN-3808 > Project: Infinispan > Issue Type: Task > Components: Querying > Reporter: Sanne Grinovero > Assignee: Adrian Nistor > -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-3807) Caching of parsed HQL queries

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-3807?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-3807: ---------------------------------- Assignee: Adrian Nistor (was: Sanne Grinovero) > Caching of parsed HQL queries > ----------------------------- > > Key: ISPN-3807 > URL: https://issues.jboss.org/browse/ISPN-3807 > Project: Infinispan > Issue Type: Enhancement > Components: Querying > Affects Versions: 6.0.0.Final > Reporter: Sanne Grinovero > Assignee: Adrian Nistor > > We'll probably need to use a cache (lowercase) to avoid invoking ANTLR on each request. > Ideally we could think of caching parameterized templates, or recognize constants: in case of constants the output could degenerate in caching a Lucene Filter. > Priority do be defined after performance tests. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-3833) QueryInterceptor#updateKnownTypesIfNeeded invokes into the cluster registry too frequently

by Sanne Grinovero (JIRA)

Sanne Grinovero created ISPN-3833: ------------------------------------- Summary: QueryInterceptor#updateKnownTypesIfNeeded invokes into the cluster registry too frequently Key: ISPN-3833 URL: https://issues.jboss.org/browse/ISPN-3833 Project: Infinispan Issue Type: Enhancement Components: Querying Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: 6.1.0.Final The QueryInterceptor should use a local cache to avoid unnecessary invocations, especially as the cluster registry is transactional this is a source of garbage generation. -- 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

11 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues December 2013