May 2016 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-6334) Handle definitions of indexable classes in server config

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6334?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6334: ---------------------------------- Fix Version/s: 9.0.0.Alpha3 (was: 9.0.0.Alpha2) > Handle definitions of indexable classes in server config > --------------------------------------------------------- > > Key: ISPN-6334 > URL: https://issues.jboss.org/browse/ISPN-6334 > Project: Infinispan > Issue Type: Feature Request > Components: Remote Querying > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.0.0.Alpha3, 9.0.0.Final > > > Server's xml config already accepts them but they are not actually used. This is a continuation of ISPN-6178. Tests for server are also missing ATM. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6224) Simplify configuration of Query with Indexing Affinity

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6224?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6224: ---------------------------------- Fix Version/s: 9.0.0.Alpha3 (was: 9.0.0.Alpha2) > Simplify configuration of Query with Indexing Affinity > ------------------------------------------------------ > > Key: ISPN-6224 > URL: https://issues.jboss.org/browse/ISPN-6224 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying > Reporter: Sanne Grinovero > Fix For: 9.0.0.Alpha3 > > > We should try to enable the "Index Affinity" capabilities in an easier way from a configuration point of view. > For example I wonder if the capabilities provided by the {{AffinityPartitioner}} could not be enabled by default, for example automatically decorating any user defined {{HashFunctionPartitioner}} so that people can't neither forget to enable it, nor override it. > Second, should it be enabled by default when the cache configuration suggests it, for example in most clustered caches? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6219) An interruption during a MassIndexer run should exit early

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6219?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6219: ---------------------------------- Fix Version/s: 9.0.0.Alpha3 (was: 9.0.0.Alpha2) > An interruption during a MassIndexer run should exit early > ---------------------------------------------------------- > > Key: ISPN-6219 > URL: https://issues.jboss.org/browse/ISPN-6219 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Reporter: Sanne Grinovero > Fix For: 9.0.0.Alpha3 > > > Methods like {{IndexUpdater.updateIndex()}} correctly check for interruption state to skip some work but they don't trigger an early exit from the indexing loop so we'd still be consuming all of the data stream. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6220) Speedup index rebuilds but using ADD rather than UPDATE statements when safe

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6220?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6220: ---------------------------------- Fix Version/s: 9.0.0.Alpha3 (was: 9.0.0.Alpha2) > Speedup index rebuilds but using ADD rather than UPDATE statements when safe > ---------------------------------------------------------------------------- > > Key: ISPN-6220 > URL: https://issues.jboss.org/browse/ISPN-6220 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying > Reporter: Sanne Grinovero > Fix For: 9.0.0.Alpha3 > > > The {{DistributedExecutorMassIndexer}} relies on update commands to index the new entries, but when we just run a full purge of the index it should be safe to use Add commands instead if we know that there aren't concurrent updates. > The lack of concurrent updates might be tricky but I think we can find such a condition when using Affinity as the index is being fully controlled by the current indexing engine, similarly to the checks to see if it's safe to use an NRT workspace. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6245) Remote query should be able to work with JBoss marshaling, compat mode and hibernate-search annotations

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6245?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6245: ---------------------------------- Fix Version/s: 9.0.0.Alpha3 (was: 9.0.0.Alpha2) > Remote query should be able to work with JBoss marshaling, compat mode and hibernate-search annotations > ------------------------------------------------------------------------------------------------------- > > Key: ISPN-6245 > URL: https://issues.jboss.org/browse/ISPN-6245 > Project: Infinispan > Issue Type: Enhancement > Components: Remote Querying > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.0.0.Alpha3 > > > This currently requires protobuf marshalling but it should be possible to make it work with JBoss marshalling too. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6585) Persistence support in functional API

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6585?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6585: ---------------------------------- Fix Version/s: 9.0.0.Alpha3 (was: 9.0.0.Alpha2) > Persistence support in functional API > ------------------------------------- > > Key: ISPN-6585 > URL: https://issues.jboss.org/browse/ISPN-6585 > Project: Infinispan > Issue Type: Sub-task > Components: Core > Reporter: Radim Vansa > Assignee: Galder Zamarreño > Fix For: 9.0.0.Alpha3 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6572) Improve JCache Remote behaviour when Management port unavailable

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6572?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6572: ---------------------------------- Fix Version/s: 9.0.0.Alpha3 (was: 9.0.0.Alpha2) > Improve JCache Remote behaviour when Management port unavailable > ---------------------------------------------------------------- > > Key: ISPN-6572 > URL: https://issues.jboss.org/browse/ISPN-6572 > Project: Infinispan > Issue Type: Enhancement > Components: JCache, Remote Protocols > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 9.0.0.Alpha3, 9.0.0.Final > > > * Checking the existence of a cache should be done using RemoteCacheManager.getCache() to avoid the need to check cache existence via Management port. > * If Management port connection fails, the transaction should be laundered into an Exception that is more meaningful for the end user. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6479) CacheRpcCommandExternalizer should cache the cache name bytes

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6479?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6479: ---------------------------------- Fix Version/s: 9.0.0.Alpha3 (was: 9.0.0.Alpha2) > CacheRpcCommandExternalizer should cache the cache name bytes > ------------------------------------------------------------- > > Key: ISPN-6479 > URL: https://issues.jboss.org/browse/ISPN-6479 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 8.2.1.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 9.0.0.Alpha3 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6491) Remove total order thread pool.

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6491?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6491: ---------------------------------- Fix Version/s: 9.0.0.Alpha3 (was: 9.0.0.Alpha2) > Remove total order thread pool. > ------------------------------- > > Key: ISPN-6491 > URL: https://issues.jboss.org/browse/ISPN-6491 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Fix For: 9.0.0.Alpha3 > > > The thread pool was deprecated and it is no longer used since long time ago. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6478) Netty worker thread starvation with events

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6478?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6478: ---------------------------------- Fix Version/s: 9.0.0.Alpha3 (was: 9.0.0.Alpha2) > Netty worker thread starvation with events > ------------------------------------------ > > Key: ISPN-6478 > URL: https://issues.jboss.org/browse/ISPN-6478 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 8.2.1.Final > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Priority: Blocker > Fix For: 9.0.0.Alpha3, 9.0.0.Final > > > As a result of ISPN-6005, we decoupled the incoming Hot Rod server invocations from sending events by adding a intermediate queue that maintains the events to send to clients. However, this separation can lead to a Netty worker thread starvation issue since we add the events to the queue in Netty's IO thread, so if the queue is full, incoming requests are stuck. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 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 May 2016