September 2010 - infinispan-issues

[JBoss JIRA] Created: (ISPN-607) Add utility class to fetch the ReplicationQueue from the cache

by craig bomba (JIRA)

Add utility class to fetch the ReplicationQueue from the cache --------------------------------------------------------------- Key: ISPN-607 URL: https://jira.jboss.org/browse/ISPN-607 Project: Infinispan Issue Type: Feature Request Components: Core API Reporter: craig bomba Assignee: craig bomba Priority: Minor We needed to be able to get a hold of the ReplicationQueue so that we could add listeners to it. org.infinispan.util.CacheUtil Essentially copies the code from TestingUtil.extractComponent although it provides a getReplicationQueue method rather than requiring ReplicationQueue.class as a parameter. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

2
5
0 / 0

[JBoss JIRA] Updated: (ISPN-180) Colocated nodes should be handled in DIST

by Vladimir Blagojevic (JIRA)

[ https://jira.jboss.org/browse/ISPN-180?page=com.atlassian.jira.plugin.sys... ] Vladimir Blagojevic updated ISPN-180: ------------------------------------- Priority: Critical (was: Major) > Colocated nodes should be handled in DIST > ----------------------------------------- > > Key: ISPN-180 > URL: https://jira.jboss.org/browse/ISPN-180 > Project: Infinispan > Issue Type: Feature Request > Components: Distributed Cache > Reporter: Manik Surtani > Assignee: Vladimir Blagojevic > Priority: Critical > Fix For: 4.2.0.BETA1, 4.2.0.Final > > > DefaultConsistentHash should place addresses on the hash wheel such that colocated nodes are never less than repl_count nodes apart to prevent data loss when a server fails. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

1
0
0 / 0

[JBoss JIRA] Commented: (ISPN-39) Distributed executors

by Ming Fai Ma (JIRA)

[ https://jira.jboss.org/browse/ISPN-39?page=com.atlassian.jira.plugin.syst... ] Ming Fai Ma commented on ISPN-39: --------------------------------- just for your reference, Hazelcast provide distributed execution with simple APIs: http://www.hazelcast.com/documentation.jsp#DistributedExecution map-reduce would be more powerful but it may be a good idea to support a simple scenario to send a Runnable to run on another node. Hazelcast is probably the only distributed execution framework that cannot transfer class definition on the wire. Gridgain and DAC (http://www.dacframe.org/trac/dac/, i never tried this one) can send class definition to other nodes for execution. The wiki page doesn't seem to have mentioned whether it will support transferring class definition. > Distributed executors > --------------------- > > Key: ISPN-39 > URL: https://jira.jboss.org/browse/ISPN-39 > Project: Infinispan > Issue Type: Feature Request > Components: RPC > Reporter: Manik Surtani > Assignee: Vladimir Blagojevic > Priority: Critical > 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 contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (ISPN-599) document CacheManager's default constructor

by Mircea Markus (JIRA)

document CacheManager's default constructor ------------------------------------------- Key: ISPN-599 URL: https://jira.jboss.org/browse/ISPN-599 Project: Infinispan Issue Type: Feature Request Reporter: Mircea Markus Assignee: Manik Surtani Fix For: 4.1.0.CR3 Current javadoc says: /** * Constructs and starts a default instance of the CacheManager, using configuration defaults. */ public DefaultCacheManager() { this(null, null, true); } This does not make it to the user what "configuration defaults" are: e.g. load from a default file, what is the default cache mode etc. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (ISPN-610) Apply isStateTransferEnabled attribute to consumer only

by craig bomba (JIRA)

Apply isStateTransferEnabled attribute to consumer only ------------------------------------------------------- Key: ISPN-610 URL: https://jira.jboss.org/browse/ISPN-610 Project: Infinispan Issue Type: Feature Request Components: Core API Reporter: craig bomba Assignee: craig bomba Priority: Minor Attachments: infinispan-core-state-trans.jar We needed to be able to configure state transfer providers and consumers separately. The short term strategy is to make each node a provider. We then use the 'fetchInMemoryState' attribute to determine if a node can be a consumer or not. org.infinispan.factories.StateTransferManagerFactory Updated to remove the 'isStateTransferEnabled' check. Now every node is a state transfer provider. org.infinispan.statetransfer.StateTransferManagerImpl public void start() Updated to now check the 'fetchInMemoryState' attribute to determine if this node can operate as a consumer. public void generateState() Updated so that any node can generate the state. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

2
8
0 / 0

[JBoss JIRA] Created: (ISPN-624) QueryInterceptor injected after LockingInterceptor - hence doesn't work with distributed mode

by Manik Surtani (JIRA)

QueryInterceptor injected after LockingInterceptor - hence doesn't work with distributed mode --------------------------------------------------------------------------------------------- Key: ISPN-624 URL: https://jira.jboss.org/browse/ISPN-624 Project: Infinispan Issue Type: Bug Components: Querying Affects Versions: 4.1.0.CR3 Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 4.1.0.Final See forum thread for details. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

2
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues September 2010