On Tue, Jul 26, 2016 at 1:43 AM, Semyon Boikov <sboi...@gridgain.com> wrote:
> We already have similar issue reproduced in our benchmarks - > https://issues.apache.org/jira/browse/IGNITE-3300. I think this is > related to optimziation done in 1.6 to store key partition in the cache > key. I believe fix will be included in 1.7 release. > This issue has no updates in Jira. Semyon, it is assigned to you. Are you working on it? > > On Tue, Jul 26, 2016 at 2:13 AM, Valentin Kulichenko < > valentin.kuliche...@gmail.com> wrote: > >> Crossposting to dev@ >> >> Folks, >> >> I noticed the exception below in couple of user threads already. This >> actually means that partition number for the key is -1, which doesn't make >> much sense to me. Does anyone has any ideas? >> >> Caused by: java.lang.ArrayIndexOutOfBoundsException: -1 >> at java.util.ArrayList.elementData(ArrayList.java:400) >> at java.util.ArrayList.get(ArrayList.java:413) >> at >> org.apache.ignite.internal.processors.affinity.GridAffinityAssignment.get(GridAffinityAssignment.java:152) >> at >> org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.nodes(GridAffinityAssignmentCache.java:387) >> at >> org.apache.ignite.internal.processors.cache.GridCacheAffinityManager.nodes(GridCacheAffinityManager.java:251) >> at >> org.apache.ignite.internal.processors.cache.GridCacheAffinityManager.primary(GridCacheAffinityManager.java:287) >> at >> org.apache.ignite.internal.processors.cache.GridCacheAffinityManager.primary(GridCacheAffinityManager.java:278) >> at >> org.apache.ignite.internal.processors.cache.GridCacheAffinityManager.primary(GridCacheAffinityManager.java:302) >> at >> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$7$3.apply(IgniteH2Indexing.java:1730) >> at >> org.apache.ignite.internal.processors.query.h2.opt.GridH2IndexBase$FilteringIterator.accept(GridH2IndexBase.java:251) >> at >> org.apache.ignite.internal.processors.query.h2.opt.GridH2IndexBase$FilteringIterator.accept(GridH2IndexBase.java:200) >> at >> org.apache.ignite.internal.util.lang.GridFilteredIterator.hasNext(GridFilteredIterator.java:59) >> at >> org.apache.ignite.internal.processors.query.h2.opt.GridH2Cursor.next(GridH2Cursor.java:59) >> at org.h2.index.IndexCursor.next(IndexCursor.java:274) >> at org.h2.table.TableFilter.next(TableFilter.java:359) >> at org.h2.command.dml.Select.queryFlat(Select.java:527) >> at org.h2.command.dml.Select.queryWithoutCache(Select.java:632) >> at org.h2.command.dml.Query.query(Query.java:297) >> at org.h2.command.dml.Query.query(Query.java:284) >> at org.h2.command.dml.Query.query(Query.java:36) >> at org.h2.command.CommandContainer.query(CommandContainer.java:91) >> at org.h2.command.Command.executeQuery(Command.java:196) >> ... 26 more >> >> >> -Val >> >> >> On Mon, Jul 25, 2016 at 5:07 AM, ght230 <ght...@163.com> wrote: >> >>> ignite-related.xml >>> < >>> http://apache-ignite-users.70518.x6.nabble.com/file/n6516/ignite-related.xml >>> > >>> Please refer to the attachment. >>> >>> >>> >>> >>> -- >>> View this message in context: >>> http://apache-ignite-users.70518.x6.nabble.com/ArrayIndexOutOfBoundsException-happened-when-doing-qurey-in-version-1-6-0-tp6245p6516.html >>> Sent from the Apache Ignite Users mailing list archive at Nabble.com. >>> >> >> >
