March 2010 - infinispan-issues - Jboss List Archives

[JBoss JIRA] Created: (ISPN-310) CacheLoader preload should only load as many entries as configured by eviction max entries

by Manik Surtani (JIRA)

CacheLoader preload should only load as many entries as configured by eviction max entries ------------------------------------------------------------------------------------------ Key: ISPN-310 URL: https://jira.jboss.org/jira/browse/ISPN-310 Project: Infinispan Issue Type: Feature Request Components: Loaders and Stores Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 4.1.0.BETA1, 4.1.0.GA This will prevent loading too much into memory causing OOMs, as well as unnecessary eviction thread churn. Probably would require another CacheLoader interface method such as loadAll(int maxEntries). A default version of this method could just call loadAll() and trim the resultset to size, and more sophisticated impls could only load the necessary number of entries, such as a LIMIT SQL query for the JDBC cache stores. -- 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, 9 months

1
3
0 / 0

[JBoss JIRA] Created: (ISPN-322) BucketBasedCacheStore - insertBucket and updateBucket should be combined

by Manik Surtani (JIRA)

BucketBasedCacheStore - insertBucket and updateBucket should be combined ------------------------------------------------------------------------ Key: ISPN-322 URL: https://jira.jboss.org/jira/browse/ISPN-322 Project: Infinispan Issue Type: Task Components: Loaders and Stores Affects Versions: 4.0.0.GA Reporter: Manik Surtani Assignee: Mircea Markus Fix For: 4.1.0.BETA1, 4.1.0.GA insertBucket and updateBucket in BucketBasedCacheStore should be combined into 1 method (storeBucket?). Javadocs should be updated accordingly, to reflect that the bucket is persisted, and if it doesn't already exist, it will be created anew. 2 impls of this (FileCacheStore and CloudCacheStore) already delegate updateBucket() --> insertBucket(). The only impl that treats these 2 calls differently is the JdbcBinaryCacheStore. But this is incorrect since JdbcBinaryCacheStore.insertBucket() throws an exception if the row already exists. And this can happen if, for example, the cache store is in async mode. Or if it is shared. So the JdbcBinaryCacheStore would first have to be fixed, to use SQL such as "INSERT... OR UPDATE", e.g.: 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/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (ISPN-353) Add a single shell script to handle cache server startup

by Manik Surtani (JIRA)

Add a single shell script to handle cache server startup -------------------------------------------------------- Key: ISPN-353 URL: https://jira.jboss.org/jira/browse/ISPN-353 Project: Infinispan Issue Type: Feature Request Components: Cache Server Reporter: Manik Surtani Assignee: Galder Zamarreno Fix For: 4.1.0.ALPHA1, 4.1.0.Final Rather than having separate startup scripts for memcached and hotrod, a single script should be used, which would take in a "protocol" parameter to determine which server module to start. >From my email to infinispan-dev: "I notice you have a memcached.sh script to start the memcached server. I believe this should be something like startServer.sh, given that we are not actually starting memcached? ;) And perhaps the script could be reused for HotRod as well ... passing in a flag to specify which protocol to speak, perhaps something like: $ startServer.sh -p memcached or $ startServer.sh -p hotrod Perhaps org.infinispan.server.memcached.Main could be in the server/core module instead, and based on the protocol flag passed in, kick start the appropriate server? WDYT?" -- 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, 9 months

2
4
0 / 0

[JBoss JIRA] Created: (ISPN-358) Rename Infinispan-server-REST distribution archive to Infinispan-servers and include hotrod and memcached servers

by Manik Surtani (JIRA)

Rename Infinispan-server-REST distribution archive to Infinispan-servers and include hotrod and memcached servers ----------------------------------------------------------------------------------------------------------------- Key: ISPN-358 URL: https://jira.jboss.org/jira/browse/ISPN-358 Project: Infinispan Issue Type: Feature Request Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 4.1.0.ALPHA1, 4.1.0.Final Would need to be organised as: /memcached /hotrod /rest README-servers.txt <-- with details on what's in the 3 directories and how to start/deploy them -- 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, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (ISPN-333) Cache Loader Class Instantiated Twice

by Amin Abbaspour (JIRA)

Cache Loader Class Instantiated Twice ------------------------------------- Key: ISPN-333 URL: https://jira.jboss.org/jira/browse/ISPN-333 Project: Infinispan Issue Type: Bug Components: Loaders and Stores Affects Versions: 4.0.0.GA Reporter: Amin Abbaspour Assignee: Manik Surtani Priority: Minor Cache Loader Class Instantiated Twice. Place a static counter in the constructor and see this happen. -- 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, 9 months

2
7
0 / 0

[JBoss JIRA] Created: (ISPN-345) Upgrade Berkeley DB JE to version 4.x

by Jarek Odzga (JIRA)

Upgrade Berkeley DB JE to version 4.x ------------------------------------- Key: ISPN-345 URL: https://jira.jboss.org/jira/browse/ISPN-345 Project: Infinispan Issue Type: Feature Request Components: Loaders and Stores Affects Versions: 4.0.0.CR4 Reporter: Jarek Odzga Assignee: Manik Surtani Fix For: 4.0.0.GA Berkeley DB JE in version 4.x introduced replication. Some projects depend on this particular version (4.x and later) and it would be great if Berkeley DB JE Cache Store was upgraded. Unfortunately JE 4.x is not drop in replacement for 3.x. There are API changes e.g. Exception hierarchy etc. The latest released version of Berkeley DB JE at the moment is 4.0.92. -- 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, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (ISPN-363) Make JBoss Marshalling version explicit

by Galder Zamarreno (JIRA)

Make JBoss Marshalling version explicit --------------------------------------- Key: ISPN-363 URL: https://jira.jboss.org/jira/browse/ISPN-363 Project: Infinispan Issue Type: Task Components: Marshalling Reporter: Galder Zamarreno Assignee: Galder Zamarreno Fix For: 4.1.0.ALPHA1 Make JBoss Marshalling wire protocol version explicit to avoid relying on defaults. Currently, the version Infinispan 4.x uses is 2. -- 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, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (ISPN-364) EvictionStrategy.NONE is poorly named. Use EvictionStrategy.UNORDERED instead.

by Manik Surtani (JIRA)

EvictionStrategy.NONE is poorly named. Use EvictionStrategy.UNORDERED instead. ------------------------------------------------------------------------------- Key: ISPN-364 URL: https://jira.jboss.org/jira/browse/ISPN-364 Project: Infinispan Issue Type: Feature Request Affects Versions: 4.0.0.Final Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 4.1.0.ALPHA1, 4.1.0.Final EvictionStrategy.NONE implies that no eviction takes place. This is incorrect, it simply means that no ordering of elements take place and hence any arbitrary element may be evicted if the cache becomes too full. EvictionStrategy.UNORDERED is more accurate. Need to deprecate EvictionStrategy.NONE and provide EvictionStrategy.UNORDERED as a synonym. -- 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, 9 months

1
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues March 2010