Bug in distributed queries
by Israel Lacerra
Hi all,
I have just found a bug in my implementation of distributed queries. When
result size is more than 100 the query does not work. I'm looking into
this... as soon as I have a solution, I'll send to git.
cheers
Israel
12 years
Redesigning CacheStore and CacheLoader SPIs
by Manik Surtani
I know this is much needed, and perhaps 6.0 may be the time to do this. Do we have a list of things we want to change here?
On the back of https://community.jboss.org/message/726337#726337 it would seem that we need the ability to pass in the ConsistentHash to the CacheLoader when loading entries, so that if the cache store is shared, it can selectively load entries targeted to the node in question. Either that, or to be able to call CacheLoader.load(CacheLoaderFilter) where CacheLoaderFilter would expose a shouldLoad(Object key).
Other thoughts include better JTA integration, etc?
Cheers
Manik
--
Manik Surtani
manik(a)jboss.org
twitter.com/maniksurtani
Lead, Infinispan
http://www.infinispan.org
12 years
support for XA CacheStores in 6.0
by Mircea Markus
Hi,
This is the continuation of a conversation Tristan, Dan and myself started around adding support for XA cache stores in Infinispan 6.0. It is also related to the CacheStore API refactoring scheduled for 6.0 [1].
The problem:
When configuring an XA cache with a cache store it is possible for the cache store to end up out of sync with in-memory data. In order to overcome that we would need cache store enhancements.
Whilst this is definitely a limitation and a nice to have feature not sure that 6.0 is the time and place to start this enhancement. Why?
There doesn't seem to be any explicit demand from the community/JDG for this feature at the moment, so other features should take priority. There's also a potential workaround for this: don't configure a cache store but the user to manage the XA write in the store directly.
Wdyt?
I've also updated the documentation to clearly state that inconsistencies are possible[2].
Cheers,
Mircea
[1] https://community.jboss.org/wiki/CacheLoaderAndCacheStoreSPIRedesign
[2] https://docs.jboss.org/author/display/ISPN/CacheLoaders#CacheLoaders-Cach...
12 years
OutOfMemory:PermGenSpace
by Mircea Markus
Hi,
Rado pinged me today re some OOM errors whilst running the test suite.
This is caused by the fact that the permgen options we pass to the suite are ignored:
<argLine>-Xmx1024m -XX:MaxPermSize=1024m</argLine>
(the suite is not being forked)
In order to avoid that please update your MAVEN_OPTS, e.g.:
export MAVEN_OPTS="-Xms512m -Xmx2048m -XX:MaxPermSize=384m"
I've also updated the docs: https://docs.jboss.org/author/display/ISPN/Contributing+-+The+test+suite
Cheers,
Mircea
12 years
some TLC for the test suite
by Mircea Markus
Hi,
Here's a set of things that were fixed around the test suite and which where checked in today:
1. Dan fixed a thread leak caused by the KeyAffinityService
2. Some of the cache managers were not created through the TestCacheManagerFactory and were running over UDP. Galder fixed that.
3. Other fine tunings for reducing the overall number of threads
- min threads in the transport pool was reduce to 1 as most of the tests, by default, won't use 2 threads concurrently for the transport
- for the TCP clusters, the send now happens in user's threads. This reduced the number of threads with one thread/connection
- 1 & 3 reduced the peak number of threads from 2k+ to 1.1k and the avg number of threads even more
4. The duration of the core test suite dropped about 40%, mainly by fixing the CacheManagerNotifierTest which was taking about 4 mins to run.
On my machine it used to take about 7:20 mins to run it, now it runs in 4:10 mins.
Cheers,
Mircea
12 years
