One additional log I noticed on the server node for these SQL queries;
WARN QueryParser For join two partitioned tables join condition should contain the equality operation of affinity keys. Left side: JOBQUEUE; right side: JOBS Is this a warning or can it cause the below exception? Thanks! Am 29.07.2022 um 10:10 schrieb don.tequ...@gmx.de:
Hi, I'm getting (unreliable until now) Exception when executing SQL query in Ignite 2.13. It seems to be connected to the parameter for column UCID. When searching for "6bf1dfc9-311b-432f-9342-257400dcc59e" the below exception happens on our production server: Caused by: javax.cache.CacheException: Failed to execute map query on remote node [nodeId=a46a2ed4-e54a-4ff6-bc28-d0c89eb8ef5c, errMsg=General error: "class org.apache.ignite.IgniteCheckedException: Runtime failure on bounds: [lower=IndexSearchRowImpl [rowHnd=org.apache.ignite.internal.processors.query.h2.index.QueryIndexRowHandler@12f90758], upper=IndexSearchRowImpl [rowHnd=org.apache.ignite.internal.processors.query.h2.index.QueryIndexRowHandler@12f90758]]"; SQL statement: SELECT JQ__Z0._VAL __C0_0, J__Z1.M1 __C0_1, J__Z1.M2 __C0_2, J__Z1.M3 __C0_3 FROM "JobQueue".JOBQUEUE JQ__Z0 LEFT OUTER JOIN "Jobs".JOBS J__Z1 ON JQ__Z0._KEY = J__Z1._KEY WHERE (JQ__Z0.UCID = ?1) AND (JQ__Z0.STATUS = ?2) [50000-197]] at org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.fail(GridReduceQueryExecutor.java:239) ~[mediafan.jar:?] at org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.onFail(GridReduceQueryExecutor.java:218) ~[mediafan.jar:?] at org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.onMessage(IgniteH2Indexing.java:2225) ~[mediafan.jar:?] at org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.lambda$start$23(IgniteH2Indexing.java:2153) ~[mediafan.jar:?] at org.apache.ignite.internal.managers.communication.GridIoManager$ArrayListener.onMessage(GridIoManager.java:3482) ~[mediafan.jar:?] at org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1909) ~[mediafan.jar:?] at org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1530) ~[mediafan.jar:?] at org.apache.ignite.internal.managers.communication.GridIoManager.access$5300(GridIoManager.java:243) ~[mediafan.jar:?] at org.apache.ignite.internal.managers.communication.GridIoManager$9.execute(GridIoManager.java:1423) ~[mediafan.jar:?] at org.apache.ignite.internal.managers.communication.TraceRunnable.run(TraceRunnable.java:55) ~[mediafan.jar:?] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) ~[?:?] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) ~[?:?] ... 1 more I've not yet seen this issue on my development servers with the same search value for UCID. For other (even little longer UCID values) it works well. Any idea what this "Runtime failure on bounds" means? There's an index on UCID, maybe it's too small? Usually UCID is a normal String value, but maybe in this case it's wrongly interpreted as UUID value and then causing an issue? Thanks!
