June 2009 - infinispan-issues - Jboss List Archives

[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, 7 months

10
32
0 / 0

[JBoss JIRA] Created: (ISPN-83) Remove dependency on JGroups FLUSH

by Manik Surtani (JIRA)

Remove dependency on JGroups FLUSH ---------------------------------- Key: ISPN-83 URL: https://jira.jboss.org/jira/browse/ISPN-83 Project: Infinispan Issue Type: Task Affects Versions: 4.0.0.GA Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 4.1.0.BETA1, 4.1.0.GA FLUSH is needed to control messages not being sent when a new view is installed, as we have observed that without this, messages get dropped by the joiner. We need to find a better way to deal with this as FLUSH is expensive and not very scalable. -- 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, 10 months

4
28
0 / 0

[JBoss JIRA] Created: (ISPN-96) Generate configuration XSD schema and parse configuration XML files

by Vladimir Blagojevic (JIRA)

Generate configuration XSD schema and parse configuration XML files -------------------------------------------------------------------- Key: ISPN-96 URL: https://jira.jboss.org/jira/browse/ISPN-96 Project: Infinispan Issue Type: Task Affects Versions: 4.0.0.ALPHA4 Reporter: Vladimir Blagojevic Assignee: Vladimir Blagojevic Fix For: 4.0.0.BETA1 Currently we have a hand maintained XSD schema and manual processing/reading of XML configuration documents. If we introduce annotations for configuration elements we could automatically create XSD schema as well as automatically read XML configuration files. The end results is much less maintenance for configuration part of 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

14 years, 1 month

2
6
0 / 0

[JBoss JIRA] Created: (ISPN-89) Document all configuration options available in XML and the Configuration beans on the wiki

by Manik Surtani (JIRA)

Document all configuration options available in XML and the Configuration beans on the wiki ------------------------------------------------------------------------------------------- Key: ISPN-89 URL: https://jira.jboss.org/jira/browse/ISPN-89 Project: Infinispan Issue Type: Task Components: Configuration Reporter: Manik Surtani Assignee: Galder Zamarreño Fix For: 4.0.0.GA This used to be in the User Guide of JBC, and now since we don't have a User Guide and everything is maintained on the wiki, we need a table on the wiki. Perhaps something that looks like this: http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs... Should explain each XML element, attribute, allowed values, default values, and equivalent setter in the Configuration bean. -- 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

14 years, 1 month

3
15
0 / 0

[JBoss JIRA] Created: (ISPN-97) Improve configuration processing and maintenance

by Vladimir Blagojevic (JIRA)

Improve configuration processing and maintenance ------------------------------------------------ Key: ISPN-97 URL: https://jira.jboss.org/jira/browse/ISPN-97 Project: Infinispan Issue Type: Task Affects Versions: 4.0.0.ALPHA4 Reporter: Vladimir Blagojevic Assignee: Vladimir Blagojevic Fix For: 4.0.0.BETA1 In order to improve configuration processing and maintenance we have to use Java annotations. We could keep all current configuration beans, that is all subclasses of AbstractConfigurationBean but introduce annotation(s) for those beans that would: - annotate each bean setter with a reference to the XML element in question (full path to it - e.g., infinispan/namedCache/cluster/sync) - provide default configuration value - describe human readable documentation for each configuration option in plain english - references to classes to process certain complex elements and others as the need arise. Furthermore we could also: - remove current hand maintained schema - create schema by automated tools given metadata in annotations - create all human readable documentation from these annotations for manuals. wiki etc etc - read all configuration elements from xml configuration files using metadata in annotations thus avoiding "by hand" reading we have now -- 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

14 years, 1 month

2
6
0 / 0

[JBoss JIRA] Created: (ISPN-95) Create interactive tutorial on using Infinispan

by Manik Surtani (JIRA)

Create interactive tutorial on using Infinispan ----------------------------------------------- Key: ISPN-95 URL: https://jira.jboss.org/jira/browse/ISPN-95 Project: Infinispan Issue Type: Task Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 4.0.0.BETA1, 4.0.0.GA Should be a wiki page that takes the user through a set of examples, in an interactive fashion. 1. Use Groovy as an interactive console (specify that interactive Java console of choice could be used: BeanShell, Jython, JRuby, even Scala) 2. Basic usage: create cache manager, create cache, put, remove, get, replace, putIfAbsent, size. Demonstrate use of lifespans and maxAge 3. Configure with a transaction manager, demonstrate transactional use 4. Configure with a cache store. Demonstrate how state is persisted. Restart cache, to demonstrate durability of cached data. 5. Configure with eviction. Demonstrate eviction with FIFO. 6. Configure with eviction and a cache store. Demonstrate FIFO + storage 7. Configure with REPL_SYNC + transactions. Start 2 shell instances, and demonstrate caches replicating put, get, remove. Demonstrate with transactions as well. For each of the above, we should create a configuration file. sample-configurations.xml, with several named caches - 'Local', 'LocalTx', 'CacheStore', 'Eviction', 'CacheStoreEviction', 'ReplicatedTx'. This sample cfg file should be shipped with the distribution so that people can refer to 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

14 years, 5 months

2
9
0 / 0

[JBoss JIRA] Created: (ISPN-87) review sample JGroups config files with jgroups team

by Mircea Markus (JIRA)

review sample JGroups config files with jgroups team ---------------------------------------------------- Key: ISPN-87 URL: https://jira.jboss.org/jira/browse/ISPN-87 Project: Infinispan Issue Type: Feature Request Reporter: Mircea Markus Assignee: Manik Surtani Fix For: 4.0.0.GA Make sure that we supply tuned sample jgroups file with our configurations. -- 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

14 years, 5 months

2
6
0 / 0

[JBoss JIRA] Created: (ISPN-104) Update release script

by Manik Surtani (JIRA)

Update release script --------------------- Key: ISPN-104 URL: https://jira.jboss.org/jira/browse/ISPN-104 Project: Infinispan Issue Type: Task Reporter: Manik Surtani Assignee: Navin Surtani Priority: Minor Fix For: 4.0.0.BETA1 The release script (written in Python) needs to be updated to: 1. Include JMX docs 2. Include config guide (ISPN-89) 3. Update docs with Google Analytics tags (currently done by running bin/updateTracker.sh manually before uploading docs) 4. Upload javadocs to SourceForge 5. Upload release files to SourceForge (SourceForge has an API for this) 6. Upload XSD schema to www.infinispan.org (need to check with the JBoss.org team on how to do this programmatically. Currently done via the CMS interface) -- 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

14 years, 5 months

1
4
0 / 0

[JBoss JIRA] Created: (ISPN-100) test Infinispan binding to JNDI

by Mircea Markus (JIRA)

test Infinispan binding to JNDI ------------------------------- Key: ISPN-100 URL: https://jira.jboss.org/jira/browse/ISPN-100 Project: Infinispan Issue Type: Feature Request Reporter: Mircea Markus Assignee: Manik Surtani Fix For: 4.0.0.GA This is related to a forum post(http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4235108#423.... a serialization exception appeared when trying to bind JBossCache instance in JNDI; same should hapend for Infinispan. Though I wouldn't expect the CacheDelegate to be serialized, this JIRA is for checking that binding a Infinispan instance can be placed in JNDI. -- 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

14 years, 5 months

2
1
0 / 0

[JBoss JIRA] Created: (ISPN-105) Support creating JdbcXXXCacheStore from JNDI-Datasource

by Klaus Friedel (JIRA)

Support creating JdbcXXXCacheStore from JNDI-Datasource ------------------------------------------------------- Key: ISPN-105 URL: https://jira.jboss.org/jira/browse/ISPN-105 Project: Infinispan Issue Type: Feature Request Components: Loaders and Stores Affects Versions: 4.0.0.ALPHA5 Reporter: Klaus Friedel Assignee: Manik Surtani In an JavaEE environment JDBC connections are created from Datasources so it should be possible to create a JdbcXXXCacheStore from a JNDI Datasource. -- 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

14 years, 6 months

3
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues June 2009