subject:"\[WARNING\]\[query\-#491%ServerNode%\]\[IgniteH2Indexing\] Query execution is too long"

Re: [WARNING][query-#491%ServerNode%][IgniteH2Indexing] Query execution is too long

2019-07-03 Thread Denis Magda

Please get to know best practices for performance optimizations: https://apacheignite-sql.readme.io/docs/performance-and-debugging As Ilya suggested, your queries just need extra optimization steps. - Denis On Tue, Jul 2, 2019 at 6:49 AM siva wrote: > Hi, > I am using Apache Ignite v2.7.5 as

Re: [WARNING][query-#491%ServerNode%][IgniteH2Indexing] Query execution is too long

2019-07-02 Thread Ilya Kasnacheev

Hello! I can see that you are selecting whole table. It is recommended to use LIMIT clause or use lazy=true (available as JDBC connection parameter and as SqlFieldsQuery setter). Regards, -- Ilya Kasnacheev вт, 2 июл. 2019 г. в 16:49, siva : > Hi, > I am using Apache Ignite v2.7.5 as thincli

[WARNING][query-#491%ServerNode%][IgniteH2Indexing] Query execution is too long

2019-07-02 Thread siva

Hi, I am using Apache Ignite v2.7.5 as thinclient and server in .net core and running in window vm. After getting long running query warning, server getting down. Server log: -- ignite-15e6d7d4.log