January 2010 - infinispan-issues - Jboss List Archives

[JBoss JIRA] Created: (ISPN-262) Geographically distributed data grid

by Manik Surtani (JIRA)

Geographically distributed data grid ------------------------------------ Key: ISPN-262 URL: https://jira.jboss.org/jira/browse/ISPN-262 Project: Infinispan Issue Type: Feature Request Components: Distributed Cache, RPC, State transfer Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 5.0.0.BETA1, 5.0.0.GA WAN replication, either Live-Live or Live-Standby. Some interesting thoughts can be gleaned from JBCACHE-816 -- 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
2
0 / 0

[JBoss JIRA] Created: (ISPN-311) CacheLoader.loadKeys(), and performance improvements when rehashing from a cache store

by Manik Surtani (JIRA)

CacheLoader.loadKeys(), and performance improvements when rehashing from a cache store -------------------------------------------------------------------------------------- Key: ISPN-311 URL: https://jira.jboss.org/jira/browse/ISPN-311 Project: Infinispan Issue Type: Feature Request Components: Distributed Cache, Loaders and Stores Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 4.1.0.BETA1, 4.1.0.GA Rehashing can be improved a bit, specifically with the addition of something like CacheLoader.loadKeys(Set<Object> excludes). This will allow the rehash code to load just the necessary keys, excluding keys already considered from the data container directly, and then inspect each key to test if the key needs to be rehashed elsewhere. If so, the value could be loaded using load(), considering that as cluster sizes increase, rehashing would only affect a smaller percentage of overall data. -- 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

1
1
0 / 0

[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, 1 month

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, 1 month

1
2
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, 2 months

2
7
0 / 0

[JBoss JIRA] Created: (ISPN-173) Build memcached server module

by Manik Surtani (JIRA)

Build memcached server module ----------------------------- Key: ISPN-173 URL: https://jira.jboss.org/jira/browse/ISPN-173 Project: Infinispan Issue Type: Feature Request Components: Cache Server Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 4.1.0.BETA1, 4.1.0.GA This server module will speak the memcached TEXT protocol and delegate to an in-VM cache. -- 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, 2 months

2
13
0 / 0

[JBoss JIRA] Created: (ISPN-314) Enhance test fwk to report when a resource was not properly cleaned by a test

by Mircea Markus (JIRA)

Enhance test fwk to report when a resource was not properly cleaned by a test ----------------------------------------------------------------------------- Key: ISPN-314 URL: https://jira.jboss.org/jira/browse/ISPN-314 Project: Infinispan Issue Type: Feature Request Reporter: Mircea Markus Assignee: Manik Surtani Fix For: 4.0.0.GA if a test fails and didn't clean up resources properly (in this case destroy the cache managers) then next test running on the same thread will see the already existing cluster, and blockUntil.. methods will fail. Make the fwk report that a cluster is not properly shutdown by a test, when another tries to create a cluster. -- 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, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (ISPN-323) Indentify tests not cleaning up their CacheManager

by Sanne Grinovero (JIRA)

Indentify tests not cleaning up their CacheManager -------------------------------------------------- Key: ISPN-323 URL: https://jira.jboss.org/jira/browse/ISPN-323 Project: Infinispan Issue Type: Task Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: 4.0.0.GA Currently some tests forget to properly kill the cacheManager after usage, not failing themselves but making other tests fail. The test causing the trouble can be identified by using a TestNG listener. -- 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, 2 months

3
7
0 / 0

[JBoss JIRA] Created: (ISPN-300) Demo memcached being accessed from a non-Java client

by Galder Zamarreno (JIRA)

Demo memcached being accessed from a non-Java client ---------------------------------------------------- Key: ISPN-300 URL: https://jira.jboss.org/jira/browse/ISPN-300 Project: Infinispan Issue Type: Task Components: Cache Server Reporter: Galder Zamarreno Assignee: Manik Surtani Fix For: 4.1.0.GA <manik> Are you going to demo the memcached server using a non-JVM client? <manik> E.g., Python? <galderz> manik, maybe at some point, that'd be a good demo <manik> http://pypi.python.org/pypi/python-memcached/1.40 <galderz> i'll create a jira for 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, 2 months

1
5
0 / 0

[JBoss JIRA] Created: (ISPN-341) Incr/Decr returns in memcached module appear to be incorrect

by Galder Zamarreno (JIRA)

Incr/Decr returns in memcached module appear to be incorrect ------------------------------------------------------------ Key: ISPN-341 URL: https://jira.jboss.org/jira/browse/ISPN-341 Project: Infinispan Issue Type: Bug Reporter: Galder Zamarreno Assignee: Galder Zamarreno Fix For: 4.1.0.ALPHA1 Verify this: [g@eq]~/i/code/trunk/server/memcached/src/main/resources% python sample_python_memcached_writer.py Testing set ['Simple_Key': Simple value] ... OK Testing set ['Expiring_Key' : 999 : 3] ... OK Testing increment 3 times ['Incr_Key' : starting at 1 ] ... OK FAIL: returned 50 FAIL: returned 51 FAIL: returned 52 Testing decrement 1 time ['Decr_Key' : starting at 4 ] ... OK FAIL: returned 51 Testing decrement 2 times in one call ['Multi_Decr_Key' : 3 ] ... OK FAIL: returned 50 It appears that the returned values are ASCIIs rather than numbers itself. -- 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, 2 months

1
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues January 2010