Re: Cache Exception for specific parameter values
The only other thing I can think of is that I did an upgrade to 2.12.0 On Thu, Aug 4, 2022 at 12:52 PM John Smith wrote: > Personally I think there is some sort of index corruption. I dropped the > table and recreated it and my problem went away. > I never restarted the application and it started to work again. > > Maybe you can make a copy of your table, insert the data fresh and point > your app to the copied table. And see if that works. Before doing something > as drastic as I did. > > On Fri, Jul 29, 2022 at 9:14 AM wrote: > >> Hi Taras, >> >> attached the extract from the local node log (which is a Ignite client) >> and the remote node log (which is a Ignite server with persistance >> enabled). >> >> What's really strange is that previous value "IDX_STAGE_308" seems to be >> the root cause? This is a value in column UCID but it's not related to >> the current search, except that of course the H2 DB must search through >> this column. Maybe there is invalid characters in the index from data >> rows from a few days ago? Maybe the index is broken? Why would it only >> show when this specific query is executed? >> >> Please let me know your thoughts. >> >> Thanks, >> Thomas. >> >> >> Am 29.07.2022 um 12:48 schrieb Taras Ledkov: >> > Hi, >> > >> > Could you provide the original exception from the map node? >> > It must be available at the log files of the map node. >> >
Re: Cache Exception for specific parameter values
Personally I think there is some sort of index corruption. I dropped the table and recreated it and my problem went away. I never restarted the application and it started to work again. Maybe you can make a copy of your table, insert the data fresh and point your app to the copied table. And see if that works. Before doing something as drastic as I did. On Fri, Jul 29, 2022 at 9:14 AM wrote: > Hi Taras, > > attached the extract from the local node log (which is a Ignite client) > and the remote node log (which is a Ignite server with persistance > enabled). > > What's really strange is that previous value "IDX_STAGE_308" seems to be > the root cause? This is a value in column UCID but it's not related to > the current search, except that of course the H2 DB must search through > this column. Maybe there is invalid characters in the index from data > rows from a few days ago? Maybe the index is broken? Why would it only > show when this specific query is executed? > > Please let me know your thoughts. > > Thanks, > Thomas. > > > Am 29.07.2022 um 12:48 schrieb Taras Ledkov: > > Hi, > > > > Could you provide the original exception from the map node? > > It must be available at the log files of the map node. >
Re: Cache Exception for specific parameter values
Hi Taras, attached the extract from the local node log (which is a Ignite client) and the remote node log (which is a Ignite server with persistance enabled). What's really strange is that previous value "IDX_STAGE_308" seems to be the root cause? This is a value in column UCID but it's not related to the current search, except that of course the H2 DB must search through this column. Maybe there is invalid characters in the index from data rows from a few days ago? Maybe the index is broken? Why would it only show when this specific query is executed? Please let me know your thoughts. Thanks, Thomas. Am 29.07.2022 um 12:48 schrieb Taras Ledkov: Hi, Could you provide the original exception from the map node? It must be available at the log files of the map node. 29-07-2022 04:08:37.695 [ 399] ERROR IgniteCachedJobQueue Error in job cache search(SELECT JQ._val, J.M1, J.M2, J.M3 FROM "JobQueue".JobQueue AS JQ LEFT JOIN "Jobs".Jobs AS J ON JQ._key=J._key WHERE JQ.ucid=? AND (JQ.status in (?))) : 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) [5-197]] 29-07-2022 04:08:37.695 [ 399] WARN CacheTransaction Transaction(CacheTransaction [thread=399, tx=null]) method had expection: 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) [5-197]] de.ks.mf.net.ignite.jobqueue.JobQueueException: 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) [5-197]] at de.ks.mf.net.ignite.jobqueue.IgniteCachedJobQueue.getQueueEntries(IgniteCachedJobQueue.java:412) ~[mediafan.jar:?] at de.ks.mf.net.ignite.jobqueue.JobManager$10.execute(JobManager.java:1041) ~[mediafan.jar:?] at de.ks.mf.net.ignite.cache.transaction.MediaFanCacheTransaction.start(MediaFanCacheTransaction.java:146) ~[mediafan.jar:?] at de.ks.mf.net.ignite.cache.transaction.MediaFanCacheTransaction.startWithoutTransaction(MediaFanCacheTransaction.java:75) ~[mediafan.jar:?] at de.ks.mf.net.ignite.jobqueue.JobManager.getQueueEntries(JobManager.java:1036) ~[mediafan.jar:?] at de.ks.mf.workflow.auto.vmafscore.extenc.AutoWorkflowVmafScoreExternalEncoder.loadJobTaskHistory(AutoWorkflowVmafScoreExternalEncoder.java:151) ~[mediafan.jar:?] at de.ks.mf.workflow.auto.vmafscore.extenc.AutoWorkflowVmafScoreExternalEncoder.setJob(AutoWorkflowVmafScoreExternalEncoder.java:83) ~[mediafan.jar:?] at de.ks.mf.net.NetMasterIgnite.createNewMediaSetAutoWorkflow(NetMasterIgnite.java:1639) ~[mediafan.jar:?] at de.ks.mf.net.NetMasterIgnite.createNewMediaSet(NetMasterIgnite.java:1548) ~[mediafan.jar:?] at de.ks.mf.net.NetMasterIgnite.createNewMediaSet(NetMasterIgnite.java:1533) ~[mediafan.jar:?] at de.ks.mf.plugins.builtin.MediaProducerSingleFile.produceMedia(MediaProducerSingleFile.java:168) ~[mediafan.jar:?] at de.ks.mf.plugins.external.MediaProducerAutoWorkflow.produceMedia(MediaProducerAutoWorkflow.java:29) ~[mediafan.jar:?] at de.ks.mf.net.ignite.jobqueue.JobManager.startMediaFanJob(JobManager.java:385) ~[media
Re: Cache Exception for specific parameter values
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) [5-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!
Cache Exception for specific parameter values
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) [5-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!
