May 2012 - infinispan-issues - Jboss List Archives

[JBoss JIRA] Created: (ISPN-387) Enable accessing Hot Rod servers via WebSockets

by Galder Zamarreno (JIRA)

Enable accessing Hot Rod servers via WebSockets ----------------------------------------------- Key: ISPN-387 URL: https://jira.jboss.org/jira/browse/ISPN-387 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 Add a flag to Hot Rod server configuration so that appropiate Base64 encoder/decoder can be used when interfacing with WebSocket clients. This might also require for Netty WebSocket channel handlers to be set up so that WebSocket upgrade handshaking can be dealt with independent of 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/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

3
4
0 / 0

[JBoss JIRA] Created: (ISPN-78) Large object support

by Manik Surtani (JIRA)

Large object support -------------------- Key: ISPN-78 URL: https://jira.jboss.org/jira/browse/ISPN-78 Project: Infinispan Issue Type: Feature Request Components: Core API Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 5.0.0.GA if each VM is allocated a 2GB heap and you have a 100 nodes in a grid with 1 redundant copy for each key, you have a theoretical addressable heap of 100GB. But you are limited by (half) the heap of a single VM per entry, since entries are stored whole. E.g., cache.put(k, my2GBObject) will fail since you need at least 2GB for the object + another 2GB for its serialized form. This gets worse when you try cache.put(k, my10GBObject). This *should* be possible if we have a theoretical 100GB heap. Potential solutions here are to fragment large objects, and store each fragment under separate keys. Another approach would be to directly stream objects to disk. etc. Needs thought and design, possibly a separate API to prevent 'pollution" of the more simplistic API. (JumboCache?) Re: fragmenting, issues to overcome: How many chunks to fragment into? Max size of each key could be configured, but how do we determine the size of an Object? VM instrumentation? Or perhaps the JumboCache only stores byte[]'s? -- 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

11 years, 8 months

10
32
0 / 0

[JBoss JIRA] (ISPN-1865) Update indexes only when needed

by Mathieu Lachance (JIRA)

Mathieu Lachance created ISPN-1865: -------------------------------------- Summary: Update indexes only when needed Key: ISPN-1865 URL: https://issues.jboss.org/browse/ISPN-1865 Project: Infinispan Issue Type: Enhancement Components: Querying Affects Versions: 5.1.1.FINAL Reporter: Mathieu Lachance Assignee: Sanne Grinovero // put in cache a value with 2 field, one indexed and one not indexed. Value value = new Value(); value.setNonIndexedFieldValue(123); value.setIndexedFieldValue(456); cache.put("key", value); // later... // get back value from cache and update the not indexed field Value value = cache.get("key"); value.setNonIndexedFieldValue(789); cache.put("key", value); The second put operation will trigger index to update even tough it hasn't changed. Sanne suggested : " Thinking about it, there might be some situations in which we can detect it, for example if the put is going to carry a valid return value then we could compare values in string form.. nice, please open an improvement request on JIRA!" See https://community.jboss.org/thread/195303 for complete reference -- 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

11 years, 8 months

4
6
0 / 0

[JBoss JIRA] (ISPN-1957) Improve internal data structures in the L1Manager

by Manik Surtani (JIRA)

Manik Surtani created ISPN-1957: ----------------------------------- Summary: Improve internal data structures in the L1Manager Key: ISPN-1957 URL: https://issues.jboss.org/browse/ISPN-1957 Project: Infinispan Issue Type: Feature Request Components: Distributed Cache Affects Versions: 5.1.3.FINAL Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 5.2.0.ALPHA1, 5.2.0.FINAL The L1Manager contains a multimap of keys to servers and their timestamps, to know where to send invalidation messages. This is currently implemented as a CHM of CHMs, and can be very bulky and inefficient. -- 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

11 years, 8 months

3
4
0 / 0

[JBoss JIRA] (ISPN-2022) Make MarshalledValues immutable

by Manik Surtani (JIRA)

Manik Surtani created ISPN-2022: ----------------------------------- Summary: Make MarshalledValues immutable Key: ISPN-2022 URL: https://issues.jboss.org/browse/ISPN-2022 Project: Infinispan Issue Type: Feature Request Components: Marshalling Affects Versions: 5.1.4.FINAL Reporter: Manik Surtani Assignee: Galder Zamarreño Fix For: 5.1.x, 5.2.0.ALPHA1, 5.2.0.FINAL MarshalledValues are not currently reused, so the containers could be made immutable. Different subtypes would be needed as well, i.e., {{InstanceBaisedMarshalledValue}}, where {{instance}} is {{final}} and {{raw}} then need not be volatile. {{RawBiasedMarshalledValue}}, where {{raw}} is {{final}} and {{instance}} then need not be volatile. {{serialisedSize}} and {{equalityPreferenceForInstance}} would be unnecessary. -- 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

11 years, 8 months

3
7
0 / 0

[JBoss JIRA] (ISPN-1823) Revisit internal collections used and replace with custom, high performance constructs

by Manik Surtani (JIRA)

Manik Surtani created ISPN-1823: ----------------------------------- Summary: Revisit internal collections used and replace with custom, high performance constructs Key: ISPN-1823 URL: https://issues.jboss.org/browse/ISPN-1823 Project: Infinispan Issue Type: Feature Request Components: Core API Affects Versions: 5.1.0.FINAL Reporter: Manik Surtani Assignee: Manik Surtani Priority: Critical Fix For: 5.2.0.ALPHA1, 5.2.0.FINAL Most JDK collections are too inefficient for internal use, such as within contexts, cache transactions, etc. -- 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

11 years, 8 months

3
4
0 / 0

[JBoss JIRA] (ISPN-1862) fire TransactionCompletedEvent not as part of the transaction

by Thomas Fromm (JIRA)

Thomas Fromm created ISPN-1862: ---------------------------------- Summary: fire TransactionCompletedEvent not as part of the transaction Key: ISPN-1862 URL: https://issues.jboss.org/browse/ISPN-1862 Project: Infinispan Issue Type: Enhancement Components: Core API Affects Versions: 5.1.1.FINAL Reporter: Thomas Fromm Assignee: Manik Surtani When catching TransactionCompletedEvent I would expect, the transaction is committed, especially when isTransactionSuccessful() == true. I need to perform some operations after a transaction was completed. My workaround is ATM to suspend the transaction, perform my (async) stuff, and resume it afterwards. But in case of errors after resume, I get another TransactionCompletedEvent for this transaction with isTransactionSuccessful() == false. You see, I need something like a TransactionReallyCompletedEvent :-) My change request is, that the TransactionCompletedEvents should be fired, after the transaction was committed. -- 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

11 years, 8 months

4
5
0 / 0

[JBoss JIRA] Created: (ISPN-1424) Implement non-blocking state transfer again on top of push-based state transfer

by Dan Berindei (JIRA)

Implement non-blocking state transfer again on top of push-based state transfer ------------------------------------------------------------------------------- Key: ISPN-1424 URL: https://issues.jboss.org/browse/ISPN-1424 Project: Infinispan Issue Type: Feature Request Components: State transfer Affects Versions: 5.0.1.FINAL Reporter: Dan Berindei Assignee: Dan Berindei Fix For: 5.2.0.FINAL Once we have the asymmetric caches support in we should be able to re-implement non-blocking state transfer. See the design document at http://community.jboss.org/wiki/AsymmetricCachesAndManualRehashingDesign#... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

3
2
0 / 0

[JBoss JIRA] Created: (ISPN-686) JdbcStringBasedCacheStore loads previous data from store before an insert

by Sanne Grinovero (JIRA)

JdbcStringBasedCacheStore loads previous data from store before an insert ------------------------------------------------------------------------- Key: ISPN-686 URL: https://jira.jboss.org/browse/ISPN-686 Project: Infinispan Issue Type: Bug Components: Loaders and Stores Affects Versions: 4.2.0.ALPHA2, 4.1.0.Final, 4.0.0.Final Reporter: Sanne Grinovero Assignee: Manik Surtani Fix For: 4.2.0.Final, 5.0.0.Final The JdbcStringBasedCacheStore implementation loads the previous data on an insert to find out if it should generate an UPDATE or INSERT statement, while it would perform much better to just verify if the primary key exists. On top of this, some databases provide ways to avoid the need to check at all, like MySQL's " INSERT ... ON DUPLICATE KEY UPDATE" [http://dev.mysql.com/doc/refman/5.0/en/insert-on-duplicate.html] -- 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

11 years, 8 months

7
29
0 / 0

[JBoss JIRA] (ISPN-2066) Simplify configuration of an Infinispan backend in the Hibernate Search engine of Infinispan Query

by Sanne Grinovero (JIRA)

Sanne Grinovero created ISPN-2066: ------------------------------------- Summary: Simplify configuration of an Infinispan backend in the Hibernate Search engine of Infinispan Query Key: ISPN-2066 URL: https://issues.jboss.org/browse/ISPN-2066 Project: Infinispan Issue Type: Enhancement Components: Querying Reporter: Sanne Grinovero Assignee: Manik Surtani Fix For: 5.2.0.ALPHA1 Make sure we can inject the needed caches in the Hibernate Search engine being started by Query, and also that the custom commands being sent from the engine are "routed to" the same engine again for processing on the listener side related to https://community.jboss.org/docs/DOC-18370 -- 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

11 years, 9 months

2
9
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues May 2012