Re: org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing - Query execution is too long

2017-04-27 Thread Andrey Mashenkov
issue > in one more query. Could you let us know how to what could be the issue > here. > > 02:51:52.591 [http-/172.30.8.97:8443-27] WARN > org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing - Query > execution is too long [time=3098 ms, sql='SELECT > PGE__Z

Re: org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing - Query execution is too long

2017-04-27 Thread abhijitprusty
Hi Andrew, Thanks for the reply. Removing index did helped. But we got the same issue in one more query. Could you let us know how to what could be the issue here. 02:51:52.591 [http-/172.30.8.97:8443-27] WARN org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing - Query execution

Re: org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing - Query execution is too long

2017-04-26 Thread Andrey Mashenkov
XX:MetaspaceSize=512m > > -XX:MinMetaspaceFreeRatio=20 > > -XX:NumberOfGCLogFiles=5 > > -Xloggc:/usr/share/jbossas/standalone/log/gc.log > > -Xms8g > > -Xmx12g > > -verbose:gc > > > > *From:* Abhijit Prusty [mailto:abhijitpru...@fico.com] > *Sent

RE: org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing - Query execution is too long

2017-04-24 Thread Abhijit Prusty
From: Abhijit Prusty [mailto:abhijitpru...@fico.com] Sent: Monday, April 24, 2017 4:09 PM To: user@ignite.apache.org Subject: RE: org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing - Query execution is too long Hi , These are the query we use for the cache, could you please help

RE: org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing - Query execution is too long

2017-04-24 Thread Abhijit Prusty
user@ignite.apache.org Subject: Re: org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing - Query execution is too long Hi Abhijit, Yes, three is a limitation: all PARTITIONED caches participating in same query should have same queryParallelismLevel. You can set it viaCacheConfiguration.setQ

Re: org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing - Query execution is too long

2017-04-24 Thread Andrey Mashenkov
andrey.mashen...@gmail.com] > *Sent:* Monday, April 24, 2017 3:17 PM > *To:* user@ignite.apache.org > *Subject:* Re: org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing > - Query execution is too long > > > > Hi, > > > > Looks like your query use

RE: org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing - Query execution is too long

2017-04-24 Thread Abhijit Prusty
: org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing - Query execution is too long Hi, Looks like your query use unapropriate index "CustomIgniteCacheConsumer"."SUPPRESSION_FLAG_idx": You can try to add index with better selectivity. It is possible you already have it and issue i

Re: org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing - Query execution is too long

2017-04-24 Thread Andrey Mashenkov
consumerCache = ignite.getOrCreateCache(consumerConfig); > ********** > > 09:06:33.371 [http-/172.30.72.8:8443-30] WARN > org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing - Query > execution is too long [time=3239 ms, sql='SELE

org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing - Query execution is too long

2017-04-24 Thread abhijitprusty
/172.30.72.8:8443-30] WARN org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing - Query execution is too long [time=3239 ms, sql='SELECT __Z0.INCOMING_CRID __C0_0, __Z0.ORIGINAL_CRID __C0_1, __Z0.SSN_ENCRYPT __C0_2, __Z0.FIRST_NAME __C0_3, __Z0.LAST_NAME __C0_4, __Z0.ADDRESS_LINE1 __C0_5, __Z0.CITY __C0_