You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by siva <si...@bizruntime.com> on 2019/07/02 13:48:56 UTC
[WARNING][query-#491%ServerNode%][IgniteH2Indexing] Query execution
is too long
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
<http://apache-ignite-users.70518.x6.nabble.com/file/t1379/ignite-15e6d7d4.log>
Server config xml file
--------------------------------------
server-config.xml
<http://apache-ignite-users.70518.x6.nabble.com/file/t1379/server-config.xml>
Client config xml file
-------------------------------------
client-config.xml
<http://apache-ignite-users.70518.x6.nabble.com/file/t1379/client-config.xml>
Cache config:
--------------------
I am using RAM-128GB, CPU-32.
Anything else need let me know.
Please,Any one give me suggestion,How to solve above warning,any
configuration missing?.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: [WARNING][query-#491%ServerNode%][IgniteH2Indexing] Query
execution is too long
Posted by Denis Magda <dm...@apache.org>.
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 <si...@bizruntime.com> wrote:
> 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
> <
> http://apache-ignite-users.70518.x6.nabble.com/file/t1379/ignite-15e6d7d4.log>
>
>
>
> Server config xml file
> --------------------------------------
> server-config.xml
> <
> http://apache-ignite-users.70518.x6.nabble.com/file/t1379/server-config.xml>
>
>
> Client config xml file
> -------------------------------------
> client-config.xml
> <
> http://apache-ignite-users.70518.x6.nabble.com/file/t1379/client-config.xml>
>
>
>
> Cache config:
> --------------------
>
>
> I am using RAM-128GB, CPU-32.
>
> Anything else need let me know.
> Please,Any one give me suggestion,How to solve above warning,any
> configuration missing?.
>
>
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>
Re: [WARNING][query-#491%ServerNode%][IgniteH2Indexing] Query
execution is too long
Posted by Ilya Kasnacheev <il...@gmail.com>.
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 <si...@bizruntime.com>:
> 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
> <
> http://apache-ignite-users.70518.x6.nabble.com/file/t1379/ignite-15e6d7d4.log>
>
>
>
> Server config xml file
> --------------------------------------
> server-config.xml
> <
> http://apache-ignite-users.70518.x6.nabble.com/file/t1379/server-config.xml>
>
>
> Client config xml file
> -------------------------------------
> client-config.xml
> <
> http://apache-ignite-users.70518.x6.nabble.com/file/t1379/client-config.xml>
>
>
>
> Cache config:
> --------------------
>
>
> I am using RAM-128GB, CPU-32.
>
> Anything else need let me know.
> Please,Any one give me suggestion,How to solve above warning,any
> configuration missing?.
>
>
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>