March 2011 - infinispan-issues - Jboss List Archives

[JBoss JIRA] Created: (ISPN-575) Corruption in data when using a permanent store between stop-start cycles

by Sanne Grinovero (JIRA)

Corruption in data when using a permanent store between stop-start cycles ------------------------------------------------------------------------- Key: ISPN-575 URL: https://jira.jboss.org/browse/ISPN-575 Project: Infinispan Issue Type: Bug Components: Loaders and Stores Affects Versions: 4.1.0.CR2 Reporter: Sanne Grinovero Assignee: Manik Surtani Fix For: 4.1.0.Final We verified the issue while using the Lucene Directory; using the Directory under stress leads to no issues even during long running tests of several hours. If during the same stress test a permanent store is enabled, all works still fine, until the CacheManager is stopped. No errors during the stop(), but after starting it again the checksum on some data fails and the index is unusable. -- 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, 8 months

4
19
0 / 0

[JBoss JIRA] Created: (ISPN-230) Enable JNDI binding of Cache/CacheManager out of the box

by Galder Zamarreno (JIRA)

Enable JNDI binding of Cache/CacheManager out of the box -------------------------------------------------------- Key: ISPN-230 URL: https://jira.jboss.org/jira/browse/ISPN-230 Project: Infinispan Issue Type: Feature Request Reporter: Galder Zamarreno Priority: Minor Fix For: 4.1.0.BETA1 Note that implementing this has no urgency since it does not really help Brian S for the JBoss AS integration. See: http://lists.jboss.org/pipermail/infinispan-dev/2009-October/001663.html So, I'm thinking that we could have a <jndi name="xyz"/> configuration option both at the global level (for Cache Manager) and at the Cache level. So, - if <jndi/> was present in the global section, we'd bind CacheManager to java:CacheManager - if <jndi name="xyz"/> was present in the global section, we'd bind CacheManager to java:xyz - if <jndi/> was present in the cache section, we'd bind Cache to java:<name-of-the-cache> - if <jndi name="xyz"/> was present in the cache section, we'd bind Cache to java:xyz -- 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, 8 months

3
3
0 / 0

[JBoss JIRA] Created: (ISPN-231) Replace use of ScheduledThreadPoolExecutor if affected by contention

by Galder Zamarreno (JIRA)

Replace use of ScheduledThreadPoolExecutor if affected by contention -------------------------------------------------------------------- Key: ISPN-231 URL: https://jira.jboss.org/jira/browse/ISPN-231 Project: Infinispan Issue Type: Task Reporter: Galder Zamarreno Assignee: Galder Zamarreno Priority: Minor Fix For: 4.1.0.BETA1 Verify whether JGRP-1051 affects Infinispan. -- 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, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (ISPN-279) Avoid instance MarshalledValue accross the code

by Galder Zamarreno (JIRA)

Avoid instance MarshalledValue accross the code ----------------------------------------------- Key: ISPN-279 URL: https://jira.jboss.org/jira/browse/ISPN-279 Project: Infinispan Issue Type: Task Reporter: Galder Zamarreno Assignee: Galder Zamarreno Fix For: 4.1.0.BETA1 Avoid doing things like this in EntryFactoryImpl or EventImpl and instead provide a way for key to be extracted when it somehow needs to be exported to the outside world when lazy serialization is on. if (key instanceof MarshalledValue) { key = ((MarshalledValue) key).get(); } -- 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, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (ISPN-842) FirstAvailable load balance policy for Hot Rod clients and extend reach of load balance policies

by Galder Zamarreño (JIRA)

FirstAvailable load balance policy for Hot Rod clients and extend reach of load balance policies ------------------------------------------------------------------------------------------------ Key: ISPN-842 URL: https://issues.jboss.org/browse/ISPN-842 Project: Infinispan Issue Type: Feature Request Components: Cache Server Reporter: Galder Zamarreño Assignee: Mircea Markus Fix For: 5.0.0.BETA1 Create a FirstAvailable load balance policy for Java Hot Rod clients and make sure load balance policies are used by all operations, particularly those extending AbstractKeyOperation. See forum thread for more info. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

3
12
0 / 0

[JBoss JIRA] Created: (ISPN-835) State transfer should not force all invocations to be synchronous

by Galder Zamarreño (JIRA)

State transfer should not force all invocations to be synchronous ----------------------------------------------------------------- Key: ISPN-835 URL: https://issues.jboss.org/browse/ISPN-835 Project: Infinispan Issue Type: Bug Components: RPC, State transfer Affects Versions: 4.2.0.CR4, 4.1.0.Final Reporter: Galder Zamarreño Assignee: Manik Surtani Fix For: 5.0.0.BETA1, 5.0.0.Final Enabling state transfer is forcing even asynchronous caches to become synchronous. A better way is needed to make sure state transfer works correctly (sync calls needed here) while normal replication calls remain asynchronous/ -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

5
34
0 / 0

[JBoss JIRA] Created: (ISPN-996) Create an infinispan-cdi module containing integration with CDI

by Manik Surtani (JIRA)

Create an infinispan-cdi module containing integration with CDI --------------------------------------------------------------- Key: ISPN-996 URL: https://issues.jboss.org/browse/ISPN-996 Project: Infinispan Issue Type: Feature Request Components: CDI integration Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 5.0.0.CR1, 5.0.0.FINAL Depends on SEAM-45 * Cache definition, configuration and injection * Caching content of producer methods on beans * Wiki/screencast to demonstrate usage -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

5
26
0 / 0

[JBoss JIRA] Created: (ISPN-359) Affinity accross caches - static or dynamic

by Tero Heinonen (JIRA)

Affinity accross caches - static or dynamic ------------------------------------------- Key: ISPN-359 URL: https://jira.jboss.org/jira/browse/ISPN-359 Project: Infinispan Issue Type: Feature Request Components: Distributed Cache Affects Versions: 4.0.0.Final Reporter: Tero Heinonen Assignee: Manik Surtani Programmable affinity either through: 1) statically (e.g. annotating a certain field as the key for consistent hashing) - in our case this cannot be based on the hashCode() as the affinity requirement and object identity are not directly related 2) dynamically (e.g. providing a overridable/annotatable consistentHashCode() function) This would help to assign entities (in multiple Caches), which are needed together in the same nodes (to avoid remote lookups) -- 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, 9 months

7
23
0 / 0

[JBoss JIRA] Created: (ISPN-312) Ability to group data entries

by Mindaugas Žakšauskas (JIRA)

Ability to group data entries ----------------------------- Key: ISPN-312 URL: https://jira.jboss.org/jira/browse/ISPN-312 Project: Infinispan Issue Type: Feature Request Components: Core API, Distributed Cache, Eviction, Locking and Concurrency Affects Versions: 4.0.0.CR2 Reporter: Mindaugas Žakšauskas Assignee: Manik Surtani Priority: Minor This is a spin-off from http://lists.jboss.org/pipermail/infinispan-dev/2009-December/001968.html. The requested feature would allow distinct entries to be assigned to custom arbitrary groups. Later in time those groups could be flushed on demand without any knowledge of entry keys. This feature exists in other open source cache library, see: http://www.opensymphony.com/oscache/api/com/opensymphony/oscache/base/Cac... -- 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, 9 months

7
15
0 / 0

[JBoss JIRA] Created: (ISPN-1000) PUSH based rehashing

by Manik Surtani (JIRA)

PUSH based rehashing -------------------- Key: ISPN-1000 URL: https://issues.jboss.org/browse/ISPN-1000 Project: Infinispan Issue Type: Feature Request Components: Distributed Cache Affects Versions: 4.2.0.Final Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 5.0.0.BETA2, 5.0.0.FINAL Current rehash schemes are based on a PULL of state. Joiners (and new owners after a leave) pull state from their neighbours. This JIRA is to reimplement this as a PUSH based scheme, where all nodes detect new joiners (or leavers) and analyse their internal state and determine what needs to be pushed where. The scheme should be more robust, involving far fewer RPCs and coordination, and would work better for merge views detected when partitions heal. Based on Bela's prototype on https://github.com/belaban/infinispan/tree/rebalance-changes -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

5
11
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues March 2011