September 2012 - infinispan-issues

[JBoss JIRA] (ISPN-2222) Configuration builders and parsers for Cassandra Cache Store

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-2222: ------------------------------------- Summary: Configuration builders and parsers for Cassandra Cache Store Key: ISPN-2222 URL: https://issues.jboss.org/browse/ISPN-2222 Project: Infinispan Issue Type: Feature Request Components: Loaders and Stores Reporter: Tristan Tarrant Assignee: Tristan Tarrant Fix For: 5.2.0.Final Add configuration builders and parser support to the Cassandra Cache Store -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

2
2
0 / 0

[JBoss JIRA] (ISPN-2258) StateTransferManager is not exposed as JMX MBean

by Radim Vansa (JIRA)

Radim Vansa created ISPN-2258: --------------------------------- Summary: StateTransferManager is not exposed as JMX MBean Key: ISPN-2258 URL: https://issues.jboss.org/browse/ISPN-2258 Project: Infinispan Issue Type: Bug Components: JMX, reporting and management Affects Versions: 5.2.0.Alpha3 Reporter: Radim Vansa Assignee: Mircea Markus StateTransferManager is not exposed as JMX MBean It appears that it is missing the MBean annotation. -- 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, 7 months

5
17
0 / 0

[JBoss JIRA] Created: (ISPN-1406) Make eviction.maxEntries a dynamically reconfigurable property

by Sanne Grinovero (JIRA)

Make eviction.maxEntries a dynamically reconfigurable property -------------------------------------------------------------- Key: ISPN-1406 URL: https://issues.jboss.org/browse/ISPN-1406 Project: Infinispan Issue Type: Feature Request Reporter: Sanne Grinovero Assignee: Manik Surtani in particular we will need to be able to set it to zero, to force a running node to still process requests but flush all it's state to the cacheloader in preparation for shutdown. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (ISPN-1402) Limit rate of incoming requests on Hot Rod server

by Sanne Grinovero (JIRA)

Limit rate of incoming requests on Hot Rod server ------------------------------------------------- Key: ISPN-1402 URL: https://issues.jboss.org/browse/ISPN-1402 Project: Infinispan Issue Type: Feature Request Components: Cache Server Reporter: Sanne Grinovero Assignee: Manik Surtani Fix For: 5.1.0.BETA1 Like application servers have a way to configure a limit of parallel incoming requests, if a too high number of requests is incoming some of these should be put in a queue, to protect the server performance. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

2
3
0 / 0

[JBoss JIRA] (ISPN-39) Distributed executors

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-39?page=com.atlassian.jira.plugin.sy... ] Vladimir Blagojevic updated ISPN-39: ------------------------------------ Component/s: Distributed Execution and Map/Reduce (was: RPC) > Distributed executors > --------------------- > > Key: ISPN-39 > URL: https://issues.jboss.org/browse/ISPN-39 > Project: Infinispan > Issue Type: Feature Request > Components: Distributed Execution and Map/Reduce > Reporter: Manik Surtani > Assignee: Vladimir Blagojevic > Priority: Critical > Labels: hackathon > Fix For: 5.0.0.BETA1, 5.0.0.FINAL > > > A new API to allow users to provide a Runnable/Callable and a set of keys to run this on, and the ability to move the code to where the data is and execute it there, returning results (if any) across a network. > Scope and objectives of this task are described in https://community.jboss.org/wiki/InfinispanDistributedExecutionFramework -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (ISPN-1043) Ensure properly clustered and booted cache node is used for distribtued executors and map reduce

by Vladimir Blagojevic (JIRA)

Ensure properly clustered and booted cache node is used for distribtued executors and map reduce ------------------------------------------------------------------------------------------------ Key: ISPN-1043 URL: https://issues.jboss.org/browse/ISPN-1043 Project: Infinispan Issue Type: Bug Components: Distributed Cache Affects Versions: 5.0.0.BETA1 Reporter: Vladimir Blagojevic Assignee: Vladimir Blagojevic Fix For: 5.0.0.BETA2 We have to ensure that only properly booted and clustered Infinispan cache nodes are used for distributed execution and mapreduce http://community.jboss.org/thread/165231?tstart=0 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

2
4
0 / 0

[JBoss JIRA] Created: (ISPN-1041) Ensure Callable isolation as it gets invoked across the cluster

by Vladimir Blagojevic (JIRA)

Ensure Callable isolation as it gets invoked across the cluster --------------------------------------------------------------- Key: ISPN-1041 URL: https://issues.jboss.org/browse/ISPN-1041 Project: Infinispan Issue Type: Bug Components: Distributed Cache Affects Versions: 5.0.0.BETA1 Reporter: Vladimir Blagojevic Assignee: Vladimir Blagojevic Fix For: 5.0.0.CR1 If Callable submitted for distributed execution contains mutable instance fields they might get mutated locally before being sent for a remote execution thus potentially resulting in wrong results being returned to a task invoker. Just before Callable is dispersed across cluster it gets invoked locally where instance fields of a submitted Callable can be possibly mutated; Callable is in turn sent to remote nodes with mutated values instead of "original" field values as submitted by user. We need to ensure that each execution node gets a pristine version of Callable object submitted by the user. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

2
5
0 / 0

[JBoss JIRA] Created: (ISPN-1039) Create DistributedExecutorService and MapReduce examples

by Vladimir Blagojevic (JIRA)

Create DistributedExecutorService and MapReduce examples --------------------------------------------------------- Key: ISPN-1039 URL: https://issues.jboss.org/browse/ISPN-1039 Project: Infinispan Issue Type: Task Components: Demos and Tutorials Affects Versions: 5.0.0.BETA1 Reporter: Vladimir Blagojevic Assignee: Vladimir Blagojevic Fix For: 5.0.0.FINAL Create at least a few examples/use cases for DistributedExecutorService and MapReduceTask. Include these examples into a test suite and include them into getting started wiki page for distributed execution framework. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

2
4
0 / 0

[JBoss JIRA] Created: (ISPN-1274) DefaultExecutorService uses no thread pool when it decides to invokeLocally

by Thomas Peuss (JIRA)

DefaultExecutorService uses no thread pool when it decides to invokeLocally --------------------------------------------------------------------------- Key: ISPN-1274 URL: https://issues.jboss.org/browse/ISPN-1274 Project: Infinispan Issue Type: Bug Components: Distributed Cache Affects Versions: 5.0.0.CR8 Reporter: Thomas Peuss Assignee: Manik Surtani DefaultExecutorService uses no thread pool when it decides to invokeLocally. It always uses the calling thread in this case. This leads to bad concurrency (1). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

7
9
0 / 0

[JBoss JIRA] Created: (ISPN-1129) method o.i.distexec.DefaultExecutorService.invokeAny(Collection tasks) never returns

by Mikhail Khludnev (JIRA)

method o.i.distexec.DefaultExecutorService.invokeAny(Collection tasks) never returns ------------------------------------------------------------------------------------ Key: ISPN-1129 URL: https://issues.jboss.org/browse/ISPN-1129 Project: Infinispan Issue Type: Bug Components: Core API Affects Versions: 5.0.0.CR3 Reporter: Mikhail Khludnev Assignee: Manik Surtani DefaultExecutorService.invokeAny() seems not working ever just because DistributedExecutionCompletionService seems not working too, because it never attach it's listener to tasks. I made a test, but didn't find an easy approach to fix it. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

3
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues September 2012