October 2011 - infinispan-issues - Jboss List Archives

[JBoss JIRA] Created: (ISPN-449) Streaming over Hot Rod

by Galder Zamarreno (JIRA)

Streaming over Hot Rod ---------------------- Key: ISPN-449 URL: https://jira.jboss.org/browse/ISPN-449 Project: Infinispan Issue Type: Feature Request Components: Cache Server Reporter: Galder Zamarreno Assignee: Manik Surtani Fix For: 5.0.0.BETA1, 5.0.0.Final Extend large object support/streaming to Hot Rod -- 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-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] 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] Created: (ISPN-1421) Put together a migrate to Infinispan 5.1 document

by Manik Surtani (JIRA)

Put together a migrate to Infinispan 5.1 document ------------------------------------------------- Key: ISPN-1421 URL: https://issues.jboss.org/browse/ISPN-1421 Project: Infinispan Issue Type: Task Affects Versions: 5.0.0.FINAL Reporter: Manik Surtani Assignee: Pete Muir Fix For: 5.1.0.CR1, 5.1.0.FINAL Please use this JIRA to list all incompatibilies and potential problems people may have migrating from 4.x or 5.0.x to 5.1.x. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

7
15
0 / 0

[JBoss JIRA] Created: (ISPN-1325) Config reference for 5.0 is broken

by Galder Zamarreño (JIRA)

Config reference for 5.0 is broken ---------------------------------- Key: ISPN-1325 URL: https://issues.jboss.org/browse/ISPN-1325 Project: Infinispan Issue Type: Bug Affects Versions: 5.0.0.FINAL Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 5.1.0.ALPHA1 http://docs.jboss.org/infinispan/5.0/apidocs/config.html is broken. Fix it and generate a new version that can be uploaded. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

2
6
0 / 0

[JBoss JIRA] Created: (ISPN-1189) config schema - clustering mode should validate format of the string

by Michal Linhard (JIRA)

config schema - clustering mode should validate format of the string -------------------------------------------------------------------- Key: ISPN-1189 URL: https://issues.jboss.org/browse/ISPN-1189 Project: Infinispan Issue Type: Enhancement Components: Configuration Affects Versions: 5.0.0.CR5 Reporter: Michal Linhard Assignee: Manik Surtani Priority: Minor currently the schema for the clustering mode says it's a string and the mode is decided by first letter of the string. this means that any garbage starting with the correct letter may lead to use of a specific mode e.g.: lasjadgadfg -> local rhdbhgh -> replication dfghbmjfgh -> distribution IlkHhdf -> invalidation what about forcing only the documented values "For distribution, set mode to either 'd', 'dist' or 'distribution'. For replication, use either 'r', 'repl' or 'replication'. Finally, for invalidation, 'i', 'inv' or 'invalidation'." + LOCAL -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

5
5
0 / 0

[JBoss JIRA] Created: (ISPN-1120) Wiki for putForExternalRead usage

by Galder Zamarreño (JIRA)

Wiki for putForExternalRead usage --------------------------------- Key: ISPN-1120 URL: https://issues.jboss.org/browse/ISPN-1120 Project: Infinispan Issue Type: Task Reporter: Galder Zamarreño Assignee: Galder Zamarreño Priority: Minor Fix For: 5.0.0.CR3 Create wiki on usage pattern of putForExternal() read. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

3
7
0 / 0

[JBoss JIRA] Created: (ISPN-1341) Eviction treats FIFO as LRU

by Jozef Vilkolak (JIRA)

Eviction treats FIFO as LRU --------------------------- Key: ISPN-1341 URL: https://issues.jboss.org/browse/ISPN-1341 Project: Infinispan Issue Type: Bug Components: Eviction Affects Versions: 5.0.0.FINAL Reporter: Jozef Vilkolak Assignee: Manik Surtani When a cache is created with eviction strategy set to FIFO it is actually treated as being LRU. This can be seen in org.infinispan.container.DefaultDataContainer.java. Functional test for FIFO eviction can be found at [https://svn.devel.redhat.com/repos/jboss-qa/edg/edg-functional-tests/trunk/] in the eviction-strategy module. Basically what the test does is insert 3 values into the cache then retrieves the first value(to differentiate FIFO and LRU) and inserts 4th value which sets eviction in motion because of maxEntries=3. I would expect the first entered value ("A") to be evicted instead it evicts the second ("B"). It uses the following cache configuration: {code:xml} <local-cache name="fifo" start="EAGER" batching="false" indexing="NONE"> <locking isolation="REPEATABLE_READ" acquire-timeout="20000" concurrency-level="500" striping="false" /> <eviction strategy="FIFO" max-entries="3" interval="2000"/> </local-cache> {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

5
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues October 2011