January 2012 - infinispan-issues - Jboss List Archives

[JBoss JIRA] Created: (ISPN-144) graph based deadlock detection

by Mircea Markus (JIRA)

graph based deadlock detection ------------------------------- Key: ISPN-144 URL: https://jira.jboss.org/jira/browse/ISPN-144 Project: Infinispan Issue Type: Feature Request Reporter: Mircea Markus Assignee: Manik Surtani Fix For: 4.1.0.GA current deadlock detection impl only knows to look for deadlocks between two transactions: i.e. tx1 (k1,k2) tx (k2,k1). This might be enhanced with transitive deadlock detection check: tx1(k1,k2) tx2(k2,k3) tx3(k3,k1). In the previous example, if all transactions are done acquiring first lock we result in a deadlock. Needs further thinking. -- 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

2
3
0 / 0

[JBoss JIRA] Created: (ISPN-509) Enable listeners to be hooked to Hot Rod servers

by Galder Zamarreno (JIRA)

Enable listeners to be hooked to Hot Rod servers ------------------------------------------------ Key: ISPN-509 URL: https://jira.jboss.org/browse/ISPN-509 Project: Infinispan Issue Type: Feature Request Components: Cache Server Reporter: Galder Zamarreno Assignee: Galder Zamarreno Fix For: 5.0.0.Final Enable Hot Rod servers to have listeners injected. At the moment, this would require some code to programatically start a Hot Rod server and associate the listener. This would not be nice cos such program would need to deal with command line parameters....etc. So, we need a way to put listeners into Hot Rod server. I can think of two options: - Enable listeners to be set via configuration XML. - Enable Hot Rod to be passed listeners via command line parameter and get Hot Rod to instantiating them. -- 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

6
13
0 / 0

[JBoss JIRA] (ISPN-1522) Annotated JMX components should use Jandex for faster lookups at startup

by Manik Surtani (Created) (JIRA)

Annotated JMX components should use Jandex for faster lookups at startup ------------------------------------------------------------------------ Key: ISPN-1522 URL: https://issues.jboss.org/browse/ISPN-1522 Project: Infinispan Issue Type: Enhancement Components: JMX, reporting and management Affects Versions: 5.1.0.BETA4 Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 5.2.0.FINAL Rather than doing reflection-based lookups for each component at startup, the ResourceDMBean class should make use of a build-time index, similar to what is done by the ComponentRegistry. -- 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

12 years, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (ISPN-1401) Provide an easy API to retrieve the total numer of stored entried ( clusterWideSize() )

by Sanne Grinovero (JIRA)

Provide an easy API to retrieve the total numer of stored entried ( clusterWideSize() ) --------------------------------------------------------------------------------------- Key: ISPN-1401 URL: https://issues.jboss.org/browse/ISPN-1401 Project: Infinispan Issue Type: Feature Request Reporter: Sanne Grinovero Assignee: Manik Surtani Priority: Minor This looks like easy to implement with a distributed executor and a common request. We will also need it as a building block. -- 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-1239) Graceful shutdown should be supported

by Manik Surtani (JIRA)

Graceful shutdown should be supported ------------------------------------- Key: ISPN-1239 URL: https://issues.jboss.org/browse/ISPN-1239 Project: Infinispan Issue Type: Feature Request Components: Distributed Cache Affects Versions: 5.0.0.FINAL Reporter: Manik Surtani Assignee: Dan Berindei Priority: Critical Fix For: 5.1.0.BETA1, 5.1.0.Final Currently, killing any node will result in a rehash. A mechanism for clean shutdown should also be supported, so that a rehash is *not* triggered. Useful when the entire cluster is being intentionally brought down. Need to think about how we do this; perhaps a LEAVE message that will prevent nodes triggering a rehash when a subsequent view change is detected. This could be done programmatically via a {{clean}} parameter to {{stop()}}, but we should explore alternatives here. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

3
18
0 / 0

[JBoss JIRA] (ISPN-31) JPA based cache store

by Manik Surtani (JIRA)

[ https://issues.jboss.org/browse/ISPN-31?page=com.atlassian.jira.plugin.sy... ] Manik Surtani updated ISPN-31: ------------------------------ Fix Version/s: 6.0.0.FINAL (was: 5.2.0.FINAL) Forum Reference: http://lists.jboss.org/pipermail/infinispan-dev/2009-July/000931.html (was: http://lists.jboss.org/pipermail/infinispan-dev/2009-July/000931.html) > JPA based cache store > --------------------- > > Key: ISPN-31 > URL: https://issues.jboss.org/browse/ISPN-31 > Project: Infinispan > Issue Type: Feature Request > Components: Loaders and Stores > Reporter: Manik Surtani > Assignee: Dan Berindei > Fix For: 6.0.0.FINAL > > > Store that uses JPA for persistence -- 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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1803) Pick a better default size for Marshaller object buffers

by Sanne Grinovero (JIRA)

Sanne Grinovero created ISPN-1803: ------------------------------------- Summary: Pick a better default size for Marshaller object buffers Key: ISPN-1803 URL: https://issues.jboss.org/browse/ISPN-1803 Project: Infinispan Issue Type: Enhancement Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: 5.1.1.CR1 -- 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

12 years, 3 months

2
5
0 / 0

[JBoss JIRA] (ISPN-1811) Upgrade to JGroups 3.0.4

by Manik Surtani (JIRA)

Manik Surtani created ISPN-1811: ----------------------------------- Summary: Upgrade to JGroups 3.0.4 Key: ISPN-1811 URL: https://issues.jboss.org/browse/ISPN-1811 Project: Infinispan Issue Type: Component Upgrade Affects Versions: 5.1.0.FINAL Reporter: Manik Surtani Assignee: Galder Zamarreño Fix For: 5.1.1.CR1, 5.1.1.FINAL -- 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

12 years, 3 months

3
2
0 / 0

[JBoss JIRA] (ISPN-1817) Lazily initialize executors and scheduled executors

by Manik Surtani (JIRA)

Manik Surtani created ISPN-1817: ----------------------------------- Summary: Lazily initialize executors and scheduled executors Key: ISPN-1817 URL: https://issues.jboss.org/browse/ISPN-1817 Project: Infinispan Issue Type: Feature Request Components: Core API Affects Versions: 5.1.0.FINAL Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 5.1.1.CR1, 5.1.1.FINAL Unused JDK executors can be expensive even when idle. A lazy initializing facade on first use is a better approach. -- 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

12 years, 3 months

2
2
0 / 0

[JBoss JIRA] (ISPN-1814) CacheViewsManagerImpl enters an infinite loop if a joining node is killed before installing the initial view

by Dan Berindei (JIRA)

Dan Berindei created ISPN-1814: ---------------------------------- Summary: CacheViewsManagerImpl enters an infinite loop if a joining node is killed before installing the initial view Key: ISPN-1814 URL: https://issues.jboss.org/browse/ISPN-1814 Project: Infinispan Issue Type: Bug Components: State transfer Affects Versions: 5.1.0.FINAL Reporter: Dan Berindei Assignee: Dan Berindei Fix For: 5.1.1.CR1, 5.1.1.FINAL, 5.2.0.FINAL Attachments: short_org.jboss.as.test.clustering.unmanaged.singleton.SingletonTestCase-output.txt When a node leaves the cluster gracefully, it is automatically removed from the set of joiners and from the next cache view. If, however, it leaves without sending a {{CacheViewControlCommand\{REQUEST_LEAVE\}}}, it is only handled properly if it's part of the last committed view. This is visible in the attached log (a simplified version of https://issues.jboss.org/secure/attachment/12350962/org.jboss.as.test.clu..., from ISPN-1806) The test repeatedly kills a node (node-udp-1) and starts it up again. Somehow JGroups didn't detect the killed node and when it was restarted we received a 3-node view: {noformat} 20:22:49,552 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-13,null) ISPN000094: Received new cluster view: [node-udp-0/cluster|4] [node-udp-0/cluster, node-udp-1/cluster, node-udp-1/cluster] {noformat} CacheViewsManagerImpl tried to install the new view, but obviously the killed node wasn't responding. I believe we only got an exception when the test timed out and it stopped the new {{node-udp-1}}: {noformat} 20:23:20,170 ERROR [org.infinispan.cacheviews.CacheViewsManagerImpl] (CacheViewInstaller-1,node-udp-0/cluster) ISPN000172: Failed to prepare view CacheView{viewId=6, members=[node-udp-0/cluster, node-udp-1/cluster]} for cache default, rolling back to view CacheView{viewId=5, members=[node-udp-0/cluster]}: java.util.concurrent.ExecutionException: org.infinispan.remoting.transport.jgroups.SuspectException: Suspected member: node-udp-1/cluster {noformat} However, because of the bug in CacheViewsManagerImpl, we kept trying to install a cache view with 3 nodes: {noformat} 20:23:20,226 ERROR [org.infinispan.cacheviews.CacheViewsManagerImpl] (CacheViewInstaller-1,node-udp-0/cluster) ISPN000172: Failed to prepare view CacheView{viewId=8, members=[node-udp-0/cluster, node-udp-1/cluster, node-udp-1/cluster]} for cache default, rolling back to view CacheView{viewId=7, members=[node-udp-0/cluster]}: java.util.concurrent.ExecutionException: org.infinispan.remoting.transport.jgroups.SuspectException: One or more nodes have left the cluster while replicating command CacheViewControlCommand{cache=default, type=PREPARE_VIEW, sender=node-udp-0/cluster, newViewId=8, newMembers=[node-udp-0/cluster, node-udp-1/cluster, node-udp-1/cluster], oldViewId=7, oldMembers=[node-udp-0/cluster]} {noformat} The test couldn't really stop because it was blocked waiting for a transaction commit, and the commit command was waiting for the cache view installation to end. -- 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

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 January 2012