September 2010 - infinispan-issues

[JBoss JIRA] Created: (ISPN-256) Enable Infinispan SPIs to implement their own commands

by Galder Zamarreno (JIRA)

Enable Infinispan SPIs to implement their own commands ------------------------------------------------------ Key: ISPN-256 URL: https://jira.jboss.org/jira/browse/ISPN-256 Project: Infinispan Issue Type: Feature Request Reporter: Galder Zamarreno Assignee: Galder Zamarreno Fix For: 4.1.0.BETA1 Much nicer IMHO would be a nice SPI / plug point to allow applications to extend the set of commands. Let an app create an ExtensionCommand; if that comes in off the channel pass it off to the handler the application registered. This could for example be used instead of the solution currently used in http://opensource.atlassian.com/projects/hibernate/browse/HHH-3818. In HHH-3818, the cache is used as a notification vehicle which is a bit of a hack and has some limitations for example when trying to implement a similar solution for evict(key) op. Another use case for it would be HTTP session ownership, from Brian Stansberry: (09:32:09 AM) brian_stansberry: ... it's just that only 1 server at a time s/b able to use a session (09:32:25 AM) brian_stansberry: so on failover i send an extension command requesting ownership (09:33:19 AM) brian_stansberry: there's actually a servlet spec requirement that only one server at a time access a session (09:33:23 AM) brian_stansberry: ejb spec too (09:33:37 AM) brian_stansberry: we don't properly handle that ... (09:34:18 AM) brian_stansberry: basically it's a lock ... (09:34:35 AM) brian_stansberry: that's all it is, a distributed lock (09:35:03 AM) brian_stansberry: but once you have the distributed lock it's yours until you give it up (09:35:29 AM) brian_stansberry: so once 1 request acquires it, subsequent requests to same server can just use a local lock ... (09:41:59 AM) brian_stansberry: the key thing is there should only be a cluster-wide operation once per session (09:42:11 AM) brian_stansberry: unless there is failover -- 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

13 years, 9 months

4
13
0 / 0

[JBoss JIRA] Created: (ISPN-272) recover from transaction failures

by Mircea Markus (JIRA)

recover from transaction failures --------------------------------- Key: ISPN-272 URL: https://jira.jboss.org/jira/browse/ISPN-272 Project: Infinispan Issue Type: Feature Request Components: Transactions Affects Versions: 5.0.0.GA Reporter: Mircea Markus Assignee: Manik Surtani We currently don't support any sort of recovery from transaction failures. E.g. tm.start(); database.delete(account); ispnCache.put(account); tm.commit(): At tm commit: -prepare is successful on both enlisted resources. - database.commit - fails What shall we do with the locks/state from ispnCache. Possible solutions: - configure to automatically commit/rollback after a timeout - keep locks on resources and allow manual intervention through JMX - others? -- 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

13 years, 9 months

4
19
0 / 0

[JBoss JIRA] Created: (ISPN-362) allow pluggable data container in infinispan

by Mircea Markus (JIRA)

allow pluggable data container in infinispan -------------------------------------------- Key: ISPN-362 URL: https://jira.jboss.org/jira/browse/ISPN-362 Project: Infinispan Issue Type: Feature Request Reporter: Mircea Markus Assignee: Manik Surtani In relation to http://community.jboss.org/message/529586#529586 Users might want to write their own data container and be able to plug that in infinispan. Implementing this would require: - change configuration to support an dataContainer element perhaps under "eviction" elements. This will be passed to DataContainerFacvtory, which will build an instance of the class and pass it back. Actually, in order to allow parameters to this container, it can look like: <eviction wakeUpInterval="500" maxEntries="5000"> <dataContainer class="custom.data.Conatiner"> <properties> <propery name="configParam" value="configValue"/> </properties> </dataContainer> </eviction> -- 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

13 years, 9 months

5
8
0 / 0

[JBoss JIRA] Created: (ISPN-493) Harden rehash leave process

by Vladimir Blagojevic (JIRA)

Harden rehash leave process --------------------------- Key: ISPN-493 URL: https://jira.jboss.org/browse/ISPN-493 Project: Infinispan Issue Type: Task Affects Versions: 4.1.0.BETA2, 4.0.0.Final Reporter: Vladimir Blagojevic Assignee: Vladimir Blagojevic Fix For: 5.0.0.BETA1, 5.0.0.Final We need to make sure that leave rehash process properly handles massive and rapid node failure. Massive failures: JGroups detects multiple node failures and pushes up to Infinispan views that are more "volatile" than we currently assumed (only one member at the time can leave). For example, if we have view V1={A,B,C,D,E} and massive failure causes {C,D,E} to fail, JGroups failure detection and GMS are going to install a view V2={A,B} to surviving members. LeaveTask does not handle this scenario. Rapid node failure: We need to revisit how LeaveTasks are queued up and executed/canceled during rapid node failures. Do we always cancel currently running leave tasks? At what stage are we allowed to cancel it and at what stage of a leave tasks is it better to wait for a completion of a task. -- 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

13 years, 10 months

3
6
0 / 0

[JBoss JIRA] Created: (ISPN-293) implement asynchronous get method getAsync()

by Sanne Grinovero (JIRA)

implement asynchronous get method getAsync() -------------------------------------------- Key: ISPN-293 URL: https://jira.jboss.org/jira/browse/ISPN-293 Project: Infinispan Issue Type: Feature Request Components: Core API Reporter: Sanne Grinovero Assignee: Manik Surtani Fix For: 4.0.0.CR3 Like other async methods existing it would be useful (natural) to have a method getAsync() for prefetching of data not immediately required. -- 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

13 years, 10 months

4
15
0 / 0

[JBoss JIRA] Created: (ISPN-271) Expose global information in RpcManagerImpl via CacheManager

by Galder Zamarreno (JIRA)

Expose global information in RpcManagerImpl via CacheManager ------------------------------------------------------------ Key: ISPN-271 URL: https://jira.jboss.org/jira/browse/ISPN-271 Project: Infinispan Issue Type: Feature Request Components: JMX, reporting and management, RPC Reporter: Galder Zamarreno Assignee: Galder Zamarreno Fix For: 4.1.0.BETA1 RpcManagerImpl exposes information that are both global to all caches under a cache manager and information that is specific to a cache. An idea would be to expose any global information via CacheManager mbean instead, i.e. address, cluster members And the rest, stuff that is cache specific, expose via rpc manager mbean, -- 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

13 years, 10 months

4
7
0 / 0

[JBoss JIRA] Created: (ISPN-654) Lost cache data on insert and state transfer with async DIST cache

by Erik Salter (JIRA)

Lost cache data on insert and state transfer with async DIST cache ------------------------------------------------------------------ Key: ISPN-654 URL: https://jira.jboss.org/browse/ISPN-654 Project: Infinispan Issue Type: Bug Affects Versions: 4.1.0.Final Reporter: Erik Salter Assignee: Manik Surtani We have a performance test that is putting 10K objects into a 4-node cluster, with each of the nodes on separate physical machines. We are seeing loss of data after an insert and loss of a data node. The test directions and code are attached to this JIRA. -- 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

13 years, 11 months

4
23
0 / 0

[JBoss JIRA] Created: (ISPN-133) Upgrade JClouds to a version that depends on Apache HTTP Core that fixes HTTPCORE-199

by Galder Zamarreno (JIRA)

Upgrade JClouds to a version that depends on Apache HTTP Core that fixes HTTPCORE-199 ------------------------------------------------------------------------------------- Key: ISPN-133 URL: https://jira.jboss.org/jira/browse/ISPN-133 Project: Infinispan Issue Type: Thirdparty Change Components: Loaders and Stores Reporter: Galder Zamarreno Assignee: Galder Zamarreno Fix For: 4.0.0.CR1 https://issues.apache.org/jira/browse/HTTPCORE-199 Remove temporary workaround in ISPN-119 as part of this: http://fisheye.jboss.org/browse/Infinispan/trunk/core/src/main/java/org/i... -- 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

13 years, 11 months

4
14
0 / 0

[JBoss JIRA] Created: (ISPN-376) Enable Infinispan standalone's Channel to be plugged with MessageListeners

by Galder Zamarreno (JIRA)

Enable Infinispan standalone's Channel to be plugged with MessageListeners -------------------------------------------------------------------------- Key: ISPN-376 URL: https://jira.jboss.org/jira/browse/ISPN-376 Project: Infinispan Issue Type: Feature Request Components: RPC Reporter: Galder Zamarreno Assignee: Galder Zamarreno Fix For: 5.0.0.BETA1, 5.0.0.Final Investigate what would need doing to enable Infinispan to receive a JGroups' Channel or ChannelFactory that allows users to add their own message listeners when such clients want to be sending rpcs around. Brian will be using a solution like this for the AS case but since AS is owner of the Channel, this is relatively easy for it assuming that JGroups has the right API for it. -- 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

13 years, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (ISPN-329) Move coalesced logic from Unscheduled to Scheduled Write-Behind or asynchronous cache store

by Galder Zamarreno (JIRA)

Move coalesced logic from Unscheduled to Scheduled Write-Behind or asynchronous cache store ------------------------------------------------------------------------------------------- Key: ISPN-329 URL: https://jira.jboss.org/jira/browse/ISPN-329 Project: Infinispan Issue Type: Task Components: Loaders and Stores Reporter: Galder Zamarreno Assignee: Galder Zamarreno Fix For: 4.1.0.BETA1 In the async cache store, remove coalescing of modifications from Unscheduled Write-Behind or strategy and move it to the Scheduled Write-Behind strategy. The aim of the Unscheduled strategy is to be as fast as possible. Having to deal with coalescing changes is only going to slow it down for very little gain. Coalescing changes in an schedule strategy makes a lot more sense. -- 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

13 years, 11 months

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues September 2010