March 2012 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-1588) IndexOutOfBoundsException while using clustered query

by Mathieu Lachance (Created) (JIRA)

IndexOutOfBoundsException while using clustered query ----------------------------------------------------- Key: ISPN-1588 URL: https://issues.jboss.org/browse/ISPN-1588 Project: Infinispan Issue Type: Bug Components: Querying, RPC Affects Versions: 5.1.0.BETA5 Reporter: Mathieu Lachance Assignee: Sanne Grinovero when using clustered query with dist sync mode i'm running into index out of bound exception. java.lang.IndexOutOfBoundsException: Index: 100, Size: 100 at java.util.ArrayList.RangeCheck(ArrayList.java:547) at java.util.ArrayList.get(ArrayList.java:322) at org.infinispan.query.clustered.DistributedIterator.current(DistributedIterator.java:138) at org.infinispan.query.clustered.DistributedIterator.next(DistributedIterator.java:114) at org.infinispan.query.clustered.ClusteredCacheQueryImpl.list(ClusteredCacheQueryImpl.java:136) at com.XXX.DistributedCache.cacheQueryList(DistributedCache.java:239) at com.XXX.DistributedCache.cacheQueryList(DistributedCache.java:200) at com.XXX.ClientCache.getClientsByServerId(ClientCache.java:168) at com.XXX.getClientsByServerId(ClientManager.java:157) at com.XXX$PingClient.run(PlayerBll.java:890) at java.util.TimerThread.mainLoop(Timer.java:512) at java.util.TimerThread.run(Timer.java:462) i do not have any reproductible step, but here's what i know : it only seems to happen under high contention ; when i'm running stress test. when running a stress test i might get query that return over than 100 results. tough i've also seen it happen on query that can only return few (4-6) results. i never saw the stack trace with different index and size different than 100 (it's always the exact same exception). i've also tried the lazy iterator to see if it would have a different behavior, but i get the same stack trace. is there anything i could look up in the source code to debug and maybe find the repro steps ? thanks, -- 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

12 years, 7 months

3
2
0 / 0

[JBoss JIRA] Created: (ISPN-949) Have something like Hibernate's ResultTransformer for Query results

by Sanne Grinovero (JIRA)

Have something like Hibernate's ResultTransformer for Query results ------------------------------------------------------------------- Key: ISPN-949 URL: https://issues.jboss.org/browse/ISPN-949 Project: Infinispan Issue Type: Enhancement Components: Querying Reporter: Sanne Grinovero Assignee: Manik Surtani Priority: Minor Fix For: 6.0.0.Final Be able to transform an array of projected fields into a nice object. So return a List<CustomBean>, instead of a List<Object[]> -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

2
6
0 / 0

[JBoss JIRA] (ISPN-1740) Refactor internal classes and SPIs to use new Configuration beans

by Manik Surtani (JIRA)

Manik Surtani created ISPN-1740: ----------------------------------- Summary: Refactor internal classes and SPIs to use new Configuration beans Key: ISPN-1740 URL: https://issues.jboss.org/browse/ISPN-1740 Project: Infinispan Issue Type: Enhancement Components: Configuration Affects Versions: 5.1.0.FINAL Reporter: Manik Surtani Assignee: Vladimir Blagojevic Fix For: 5.2.0.FINAL The current programmatic configuration makes use of the old 5.0.x config beans internally (injection) as well as unit tests and in SPIs (CacheStore, CommandInterceptor, etc). We need to refactor these SPIs and internal code to use the new post-5.1 config beans. However, the public API (DefaultCacheManager) should still support the old Configuration beans. To do this we'd need to write something like the reverse of the LegacyConfigurationAdapter. The LegacyConfigurationAdapter takes a 5.1 Configuration and creates a 5.0 Configuration. We need to do this in reverse once the internals start using the new 5.1 Configuration. -- 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

12 years, 7 months

3
10
0 / 0

[JBoss JIRA] (ISPN-1819) Tune River buffer sizing decision in AbstractJBossMarshaller

by Sanne Grinovero (JIRA)

Sanne Grinovero created ISPN-1819: ------------------------------------- Summary: Tune River buffer sizing decision in AbstractJBossMarshaller Key: ISPN-1819 URL: https://issues.jboss.org/browse/ISPN-1819 Project: Infinispan Issue Type: Enhancement Reporter: Sanne Grinovero Assignee: Sanne Grinovero Priority: Minor Fix For: 5.2.0.ALPHA1 -- 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

12 years, 7 months

1
2
0 / 0

[JBoss JIRA] (ISPN-1940) Query statistics via JMX

by Sanne Grinovero (JIRA)

Sanne Grinovero created ISPN-1940: ------------------------------------- Summary: Query statistics via JMX Key: ISPN-1940 URL: https://issues.jboss.org/browse/ISPN-1940 Project: Infinispan Issue Type: Feature Request Components: Querying Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: 6.0.0.FINAL -- 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

12 years, 7 months

1
1
0 / 0

[JBoss JIRA] (ISPN-1804) Implement a CacheStore optimized for GlusterFS

by Manik Surtani (JIRA)

Manik Surtani created ISPN-1804: ----------------------------------- Summary: Implement a CacheStore optimized for GlusterFS Key: ISPN-1804 URL: https://issues.jboss.org/browse/ISPN-1804 Project: Infinispan Issue Type: Feature Request Components: Loaders and Stores Affects Versions: 5.1.0.FINAL Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 5.2.0.ALPHA1, 5.2.0.FINAL -- 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

12 years, 7 months

2
2
0 / 0

[JBoss JIRA] (ISPN-1535) Implement a cachestore for HBase

by Justin Hayes (Created) (JIRA)

Implement a cachestore for HBase -------------------------------- Key: ISPN-1535 URL: https://issues.jboss.org/browse/ISPN-1535 Project: Infinispan Issue Type: Enhancement Components: Loaders and Stores Affects Versions: 5.1.0.BETA4 Reporter: Justin Hayes Assignee: Manik Surtani I have implemented a cachestore for HBase that is modeled after the Cassandra cachestore, albeit with fewer bells and whistles. I need to repurpose the code that was done for a different project and once done, I will submit a git pull request. -- 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

12 years, 7 months

3
4
0 / 0

[JBoss JIRA] (ISPN-1625) No need to throw IllegalStateException on receiving a new view on a stopped cache

by Sanne Grinovero (Created) (JIRA)

No need to throw IllegalStateException on receiving a new view on a stopped cache --------------------------------------------------------------------------------- Key: ISPN-1625 URL: https://issues.jboss.org/browse/ISPN-1625 Project: Infinispan Issue Type: Bug Components: Distributed Cache Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: 5.1.0.CR2 -- 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

12 years, 7 months

7
9
0 / 0

[JBoss JIRA] Created: (ISPN-893) Addtional attribute on @CacheEntryCreated to get on pre notifications only

by Sudheer Krishna (JIRA)

Addtional attribute on @CacheEntryCreated to get on pre notifications only ----------------------------------------------------------------------------- Key: ISPN-893 URL: https://issues.jboss.org/browse/ISPN-893 Project: Infinispan Issue Type: Enhancement Components: Listeners Affects Versions: 4.2.0.Final Environment: ALL Reporter: Sudheer Krishna Assignee: Manik Surtani Priority: Minor I may have usescases where i need notifications only when isPre = true. I was expecting a parameter to be taken by @CacheEntryCreated. But this doesnt seem to take any parametres. Aslo i would like similar values on @CacheEntryremoved also. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

4
17
0 / 0

[JBoss JIRA] Created: (ISPN-999) Support eventual consistency

by Manik Surtani (JIRA)

Support eventual consistency ---------------------------- Key: ISPN-999 URL: https://issues.jboss.org/browse/ISPN-999 Project: Infinispan Issue Type: Feature Request Components: Distributed Cache, Locking and Concurrency Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 5.1.0.BETA1, 5.1.0.Final Essentially, it is about supporting eventual consistency in Infinispan. Currently Infinispan is strongly consistent when using synchronous distribution mode. Each data owner receives updates synchronously so anyone anywhere on the cluster doing a GET will see the correct value. The only exception is during a rehash (when a new node joins or leaves), that consistency is eventual since the GET may reach a new joiner who may not have applied state it receives from its neighbours yet. However this is hidden from users since the GET is sent to> 1 data owner and if an UnsureResponse is received (determined by the fact that a new joiner responds and the new joiner wouldn't have finished applying state), the caller thread waits for more definite responses. However, there is a use case for being eventually consistent as well: the main benefits being speed and partition tolerance. E.g., if we use distribution in asynchronous mode, the writes become *much* faster. However, anyone anywhere doing a GET will have to perform the GET on all data owners, and compare the versions of the data received to determine which is the latest. And if there is a conflict, to pass back all values to the user. So in terms of design, what I have in mind is: * All cache entries are versioned using vector clocks. One vector clock per node. * When a node performs a GET, the GET is sent to all data owners (concurrently), and the value + version is retrieved from each. * If the versions are all the same (or they can be "fast forwarded"), the value is returned * Otherwise, all potential values and their versions are returned * A resolve() API should be provided where application code may provide a "hint" as to which version should be "correct" - which will cause an update. * In terms of implementation, this will touch the DistributionInterceptor, InternalCacheEntry and relevant factories, some config code (since this should be consistency model should be configurable), and a new public interface. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

4
8
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues March 2012