June 2011 - infinispan-issues - Jboss List Archives

[JBoss JIRA] Created: (ISPN-557) support for same transaction touching multiple nodes (multiple VMs)

by Mircea Markus (JIRA)

support for same transaction touching multiple nodes (multiple VMs) -------------------------------------------------------------------- Key: ISPN-557 URL: https://jira.jboss.org/browse/ISPN-557 Project: Infinispan Issue Type: Feature Request Components: Transactions Reporter: Mircea Markus Assignee: Manik Surtani Fix For: 5.1.0.Final E.g. if a distributed transaction managers touches two embedded Infinispan nodes within the same transaction. Could be implemented using the Hot Rod client approach - but in an embedded fashion! EmbeddedClient <-- implements logic above Except comms are in-VM for local entries And via RpcDispatcher for remote entries RemoteClient extends EmbeddedClient Adds proper HotRod layer for comms Including failover, smart routing, 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

12 years, 3 months

3
6
0 / 0

[JBoss JIRA] Created: (ISPN-1090) Hot Rod protocol improvements for version 2

by Galder Zamarreño (JIRA)

Hot Rod protocol improvements for version 2 ------------------------------------------- Key: ISPN-1090 URL: https://issues.jboss.org/browse/ISPN-1090 Project: Infinispan Issue Type: Enhancement Components: Cache Server Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 5.1.0.BETA1, 5.1.0.Final This JIRA will act as a place to keep track of enhancements to the Hot Rod protocol that should be included in version 2 of the protocol: - We need a new error status code so that clients can detect when a node has been suspected and so react accordingly (i.e. not bubble it up but instead failover). Currently, this can be solved by checking whether the error message contains SuspectException but this is not nice. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

6
18
0 / 0

[JBoss JIRA] Created: (ISPN-848) Enhance HotRod to allow explicit locking of keys

by Erik Salter (JIRA)

Enhance HotRod to allow explicit locking of keys ------------------------------------------------ Key: ISPN-848 URL: https://issues.jboss.org/browse/ISPN-848 Project: Infinispan Issue Type: Feature Request Reporter: Erik Salter Assignee: Manik Surtani Hot Rod clients should allow explicit locking of keys, especially useful for the "find-for-update" design pattern. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

4
6
0 / 0

[JBoss JIRA] Created: (ISPN-1116) Version-aware InternalCacheEntries

by Manik Surtani (JIRA)

Version-aware InternalCacheEntries ---------------------------------- Key: ISPN-1116 URL: https://issues.jboss.org/browse/ISPN-1116 Project: Infinispan Issue Type: Feature Request Components: Core API Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 5.1.0.BETA1, 5.1.0.Final This is to support a number of things including eventual consistency as well as tombstones for deleted entries. Further, this version would need to be used when doing MVCC concurrent write comparisons for write skews (and not just a reference check which is done at the moment). This also would need to be able to use versions provided in a value's metadata (see ISPN-1103) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

9
17
0 / 0

[JBoss JIRA] Created: (ISPN-871) Out-of-heap data container implementation

by Manik Surtani (JIRA)

Out-of-heap data container implementation ----------------------------------------- Key: ISPN-871 URL: https://issues.jboss.org/browse/ISPN-871 Project: Infinispan Issue Type: Feature Request Components: Core API Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 5.1.0.BETA1, 5.1.0.Final The DataContainer interface could be implemented using a off-heap impl in C, using mmap. It would require custom memory management (gc-lite?) to reclaim free space, as well as reimplementing of eviction algorithms to maintain the contract of a self-sizing data container, but the benefits of this would be the ability to address very large amounts of memory with minimal gc overhead from the JVM. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

6
16
0 / 0

[JBoss JIRA] Created: (ISPN-863) Eviction based on JVM memory utilization

by Dave Marion (JIRA)

Eviction based on JVM memory utilization ---------------------------------------- Key: ISPN-863 URL: https://issues.jboss.org/browse/ISPN-863 Project: Infinispan Issue Type: Enhancement Components: Eviction Affects Versions: 4.2.0.Final Environment: N/A Reporter: Dave Marion Assignee: Manik Surtani Allow user to specify percentage threshold upon which eviction will kick in and begin evicting entries based on the specified strategy. This would allow user to create a cache that will attempt to keep as many entries in memory as possible without having to specify maxEntries. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

8
38
0 / 0

[JBoss JIRA] Created: (ISPN-374) Add event handling to Hot Rod

by Galder Zamarreno (JIRA)

Add event handling to Hot Rod ----------------------------- Key: ISPN-374 URL: https://jira.jboss.org/jira/browse/ISPN-374 Project: Infinispan Issue Type: Feature Request Components: Cache Server Reporter: Galder Zamarreno Assignee: Galder Zamarreno Fix For: 5.1.0.BETA1, 5.1.0.Final Enable Hot Rod servers to send events asynchronously to registered clients over persistent connections. This would allow use cases such as clients maintaining L1 caches and these events could be used for servers to invalidate keys on the client side. See dev list thread for more info. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

3
8
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

12 years, 3 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

12 years, 3 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

12 years, 3 months

2
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues June 2011