February 2016 - infinispan-issues

[JBoss JIRA] (ISPN-5413) Index Affinity support

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-5413?page=com.atlassian.jira.plugin.... ] Sanne Grinovero reassigned ISPN-5413: ------------------------------------- Assignee: Gustavo Fernandes > Index Affinity support > ---------------------- > > Key: ISPN-5413 > URL: https://issues.jboss.org/browse/ISPN-5413 > Project: Infinispan > Issue Type: Feature Request > Components: Embedded Querying > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Fix For: 8.2.0.Beta2 > > > As described in https://github.com/infinispan/infinispan/wiki/Index-affinity-proposal -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-5413) Index Affinity support

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-5413?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-5413: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/3912 > Index Affinity support > ---------------------- > > Key: ISPN-5413 > URL: https://issues.jboss.org/browse/ISPN-5413 > Project: Infinispan > Issue Type: Feature Request > Components: Embedded Querying > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Fix For: 8.2.0.Beta2 > > > As described in https://github.com/infinispan/infinispan/wiki/Index-affinity-proposal -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-5413) Index Affinity support

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-5413?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-5413: ---------------------------------- Fix Version/s: 8.2.0.Beta2 > Index Affinity support > ---------------------- > > Key: ISPN-5413 > URL: https://issues.jboss.org/browse/ISPN-5413 > Project: Infinispan > Issue Type: Feature Request > Components: Embedded Querying > Reporter: Gustavo Fernandes > Fix For: 8.2.0.Beta2 > > > As described in https://github.com/infinispan/infinispan/wiki/Index-affinity-proposal -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6211) Create DMR operations to enable / disable rebalancing per cache and container

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6211?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6211: ---------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 8.2.0.Final Resolution: Done > Create DMR operations to enable / disable rebalancing per cache and container > ----------------------------------------------------------------------------- > > Key: ISPN-6211 > URL: https://issues.jboss.org/browse/ISPN-6211 > Project: Infinispan > Issue Type: Feature Request > Components: JMX, reporting and management > Reporter: Pedro Zapata > Assignee: Pedro Ruivo > Fix For: 8.2.0.Beta2, 8.2.0.Final > > > In order to enable and disable rebalancing in the console, we need a DMR operation that allows to change this, at the cache container level and at the cache level. > Currently, there are 2 attributes cache-rebalance and rebalancing=true related to this, but no operations to change this behaviour. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6074) DistExec API should not require a distributed cache

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-6074?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-6074: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > DistExec API should not require a distributed cache > --------------------------------------------------- > > Key: ISPN-6074 > URL: https://issues.jboss.org/browse/ISPN-6074 > Project: Infinispan > Issue Type: Enhancement > Components: Core, Distributed Execution and Map/Reduce > Reporter: Tristan Tarrant > Assignee: William Burns > Fix For: 8.2.0.Beta2, 8.2.0.Final > > > The current DistExec API has the limitation that it requires a distributed cache to choose the nodes on which it runs the code. > The distexec API should instead be based off the DefaultCacheManager. > Additionally, the API could be redesigned and possibly take inspiration from the streams API (i.e. lambdas, etc) > cacheManager.cluster().execute(<lambda>) > Add fluent methods to filter nodes by address, etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6223) Create an integration test to verify that cache api is not needed for infinispan-embedded

by Vaclav Dedik (JIRA)

Vaclav Dedik created ISPN-6223: ---------------------------------- Summary: Create an integration test to verify that cache api is not needed for infinispan-embedded Key: ISPN-6223 URL: https://issues.jboss.org/browse/ISPN-6223 Project: Infinispan Issue Type: Enhancement Affects Versions: 8.2.0.Beta1 Reporter: Vaclav Dedik Assignee: Vaclav Dedik See this PR: https://github.com/infinispan/infinispan/pull/3897 And this ticket: https://issues.jboss.org/browse/ISPN-6025 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

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

by Sanne Grinovero (JIRA)

Sanne Grinovero created ISPN-6224: ------------------------------------- Summary: 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: 8.2.0.CR1 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)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6222) Failover support for MassIndexer

by Gustavo Fernandes (JIRA)

Gustavo Fernandes created ISPN-6222: --------------------------------------- Summary: Failover support for MassIndexer Key: ISPN-6222 URL: https://issues.jboss.org/browse/ISPN-6222 Project: Infinispan Issue Type: Enhancement Reporter: Gustavo Fernandes -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6221) Support MassIndexer on local caches

by Gustavo Fernandes (JIRA)

Gustavo Fernandes created ISPN-6221: --------------------------------------- Summary: Support MassIndexer on local caches Key: ISPN-6221 URL: https://issues.jboss.org/browse/ISPN-6221 Project: Infinispan Issue Type: Enhancement Reporter: Gustavo Fernandes -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

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

by Sanne Grinovero (JIRA)

Sanne Grinovero created ISPN-6220: ------------------------------------- Summary: 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: 8.2.0.CR1 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)

10 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues February 2016