February 2014 - infinispan-issues

[JBoss JIRA] (ISPN-4011) Make it possible to use 'remote-jmx' protocol inside Karaf

by Adrian Nistor (JIRA)

Adrian Nistor created ISPN-4011: ----------------------------------- Summary: Make it possible to use 'remote-jmx' protocol inside Karaf Key: ISPN-4011 URL: https://issues.jboss.org/browse/ISPN-4011 Project: Infinispan Issue Type: Feature Request Reporter: Adrian Nistor Assignee: Martin Gencur Fix For: 7.0.0.Final This is needed so remote-query clients can register protobuf schemas via jmx. Currently this was circumvented by creating a separate stand-alone app (ProtofileRegistrar) that runs outside Karaf before the actual test. -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2284) Execute Mapper and Reducer tasks in parallel where possible

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-2284?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-2284: ------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 7.0.0.Alpha1 Resolution: Done > Execute Mapper and Reducer tasks in parallel where possible > ----------------------------------------------------------- > > Key: ISPN-2284 > URL: https://issues.jboss.org/browse/ISPN-2284 > Project: Infinispan > Issue Type: Feature Request > Components: Distributed Execution and Map/Reduce > Affects Versions: 5.2.0.Alpha3 > Reporter: Vladimir Blagojevic > Assignee: Vladimir Blagojevic > Fix For: 7.0.0.Alpha1, 7.0.0.Final > > Attachments: Infinispan-MapReduce Job Times.png > > > In our current implementation of Map/Reduce, Mapper and Reducer tasks executed on remote JVMs load and process key/values serially on a single thread. Where and if possible we should use executors to process keys/values in parallel. -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2284) Execute Mapper and Reducer tasks in parallel where possible

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-2284?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-2284: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/2300 > Execute Mapper and Reducer tasks in parallel where possible > ----------------------------------------------------------- > > Key: ISPN-2284 > URL: https://issues.jboss.org/browse/ISPN-2284 > Project: Infinispan > Issue Type: Feature Request > Components: Distributed Execution and Map/Reduce > Affects Versions: 5.2.0.Alpha3 > Reporter: Vladimir Blagojevic > Assignee: Vladimir Blagojevic > Fix For: 7.0.0.Final > > Attachments: Infinispan-MapReduce Job Times.png > > > In our current implementation of Map/Reduce, Mapper and Reducer tasks executed on remote JVMs load and process key/values serially on a single thread. Where and if possible we should use executors to process keys/values in parallel. -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-3917) Allow execution of queries on non-indexed fields

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-3917?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-3917: ---------------------------------- Labels: (was: 6.3remotequeries 630) > Allow execution of queries on non-indexed fields > ------------------------------------------------ > > Key: ISPN-3917 > URL: https://issues.jboss.org/browse/ISPN-3917 > Project: Infinispan > Issue Type: Feature Request > Components: Embedded Querying > Reporter: William Burns > Assignee: Adrian Nistor > Fix For: 7.0.0.Final > > > The cluster listeners will want to use the Query DSL for filtering and projection views. We don't want to have to tie ourselves to Lucene to do this. It was discussed to implement this using reflection. -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-3997) Expired cache entries are not pruned from memory and store on access

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3997?page=com.atlassian.jira.plugin.... ] Dan Berindei commented on ISPN-3997: ------------------------------------ [~mircea.markus], maybe we should create a feature request for this and see if there is demand for it? Size-based eviction can be done on the thread accessing the entry, with {{EvictionThreadPolicy.PIGGYBACK}}, we could do the same for expired entries. That is, unless we go with Sanne's suggestion and eliminate expiration checks in the caller thread completely... > Expired cache entries are not pruned from memory and store on access > -------------------------------------------------------------------- > > Key: ISPN-3997 > URL: https://issues.jboss.org/browse/ISPN-3997 > Project: Infinispan > Issue Type: Bug > Components: Eviction > Affects Versions: 6.0.1.Final, 7.0.0.Alpha1 > Environment: Remote HotRod access to infinispan-server > Reporter: Wolf-Dieter Fink > Assignee: Dan Berindei > > Due to the documentation expired entries are pruned by having a scheduler or if they are accessed after expiration. > This will not be done if the key is access. > In case of having no scheduler to prune the entries this might cause OutOfMemory issues. -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-3718) Select which protobuf fields to index

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-3718?page=com.atlassian.jira.plugin.... ] Sanne Grinovero commented on ISPN-3718: --------------------------------------- yes it's looking like a valid approach. It's definitely interesting for the more advanced use cases, but I think our priority is to minimize indexing cost for the simple (most common) use cases. I've written some thoughts on the mailing list about a no-metadata approach which would infer what needs to be indexed from a set of pre-defined queries. Imagine the user has to list all "SQL" queries it intends to run upfront, and from there we simply infer what kinds of indexing options are needed. My aim is of course simplification of developers experience. Having this metadata in protobuf would of course still be needed, but would be less of a priority. http://lists.jboss.org/pipermail/infinispan-dev/2014-February/014537.html > Select which protobuf fields to index > ------------------------------------- > > Key: ISPN-3718 > URL: https://issues.jboss.org/browse/ISPN-3718 > Project: Infinispan > Issue Type: Feature Request > Components: Embedded Querying > Reporter: Adrian Nistor > Assignee: Adrian Nistor > > Currently we index all fields. An interesting idea is to use a custom protobuf Option (see 'Custom Options' section here https://developers.google.com/protocol-buffers/docs/proto) to indicate which message types and specifically which fields should be indexed, similar to Hibernate Search annotations. -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-3909) Authorization for Cache and CacheManager access

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3909?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3909: -------------------------------- Labels: 630 (was: ) > Authorization for Cache and CacheManager access > ----------------------------------------------- > > Key: ISPN-3909 > URL: https://issues.jboss.org/browse/ISPN-3909 > Project: Infinispan > Issue Type: Sub-task > Components: Core, Security > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Labels: 630 > Fix For: 7.0.0.Final > > -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-3910) HotRod authentication

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3910?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3910: -------------------------------- Labels: 630 (was: ) > HotRod authentication > --------------------- > > Key: ISPN-3910 > URL: https://issues.jboss.org/browse/ISPN-3910 > Project: Infinispan > Issue Type: Sub-task > Components: Remote Protocols, Security > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Labels: 630 > Fix For: 7.0.0.Final > > -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-3917) Allow execution of queries on non-indexed fields

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3917?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3917: -------------------------------- Labels: 6.3remotequeries 630 (was: 6.3remotequeries) > Allow execution of queries on non-indexed fields > ------------------------------------------------ > > Key: ISPN-3917 > URL: https://issues.jboss.org/browse/ISPN-3917 > Project: Infinispan > Issue Type: Feature Request > Components: Embedded Querying > Reporter: William Burns > Assignee: Adrian Nistor > Labels: 6.3remotequeries, 630 > Fix For: 7.0.0.Final > > > The cluster listeners will want to use the Query DSL for filtering and projection views. We don't want to have to tie ourselves to Lucene to do this. It was discussed to implement this using reflection. -- 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

12 years, 1 month

1
0
0 / 0

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

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3983?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3983: -------------------------------- Labels: 6.3remotequeries 630 (was: 6.3remotequeries) > 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 > Fix For: 7.0.0.Alpha1, 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 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

12 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 2014