Mailing-List: contact user-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@ignite.apache.org
MIME-Version: 1.0
In-Reply-To: <1493209493165-12266.post@n6.nabble.com>
References: <1493209493165-12266.post@n6.nabble.com>
From: Andrey Mashenkov <andrey.mashenkov@gmail.com>
Date: Wed, 26 Apr 2017 16:48:08 +0300
Message-ID: <CANCAXEFXwTP1750n7jiYwMcjAMRfQeLkvgcUWqU-b6xm0q+tuA@mail.gmail.com>
Subject: Re: setting query timeout and getting partial result instead of exception.
To: user@ignite.apache.org
Content-Type: multipart/alternative; boundary=f403045f8d022b7cea054e1217bf
archived-at: Wed, 26 Apr 2017 13:49:47 -0000

--f403045f8d022b7cea054e1217bf
Content-Type: text/plain; charset=UTF-8

Hi,

You can try to increase SqlQuery.setTimeout() (30 sec by default) or
connectorConfiguration.setIdleTimeout() (7 sec by default)
It may slightly help if you use sorting, as you need to have pages of rows
from all nodes to make correct merge.

Also, you can try to increase SqlQuery.pageSize() or
JDBCStatement.fetchSize(). 1024 is default value.

On Wed, Apr 26, 2017 at 3:24 PM, neerajbhatt <neerajbhatt2000@gmail.com>
wrote:

> Hi All
>
> We have a cache which is to be partitioned across nodes.
> Currently all the SQL queries are executed on all nodes by default.
> However, if a node is slow, all the queries will be slow.
> So, is there a way to set the timeout on the SQL queries, so that even
> though a few nodes are slow and timeout, the data is returned from rest of
> the nodes.
> This way, we will get partial data, instead of exception.
>
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/setting-query-timeout-and-getting-
> partial-result-instead-of-exception-tp12266.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>


-- 
Best regards,
Andrey V. Mashenkov

--f403045f8d022b7cea054e1217bf
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi,<div><br></div><div>You can try to increase SqlQuery.se=
tTimeout() (30 sec by default) or connectorConfiguration.setIdleTimeout() (=
7 sec by default)</div><div>It may slightly help if you use sorting, as you=
 need to have pages of rows from all nodes to make correct merge.</div><div=
><br></div><div>Also, you can try to increase SqlQuery.pageSize() or JDBCSt=
atement.fetchSize(). 1024 is default value.</div></div><div class=3D"gmail_=
extra"><br><div class=3D"gmail_quote">On Wed, Apr 26, 2017 at 3:24 PM, neer=
ajbhatt <span dir=3D"ltr">&lt;<a href=3D"mailto:neerajbhatt2000@gmail.com" =
target=3D"_blank">neerajbhatt2000@gmail.com</a>&gt;</span> wrote:<br><block=
quote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc=
 solid;padding-left:1ex">Hi All<br>
<br>
We have a cache which is to be partitioned across nodes.<br>
Currently all the SQL queries are executed on all nodes by default.<br>
However, if a node is slow, all the queries will be slow.<br>
So, is there a way to set the timeout on the SQL queries, so that even<br>
though a few nodes are slow and timeout, the data is returned from rest of<=
br>
the nodes.<br>
This way, we will get partial data, instead of exception.<br>
<br>
<br>
<br>
<br>
--<br>
View this message in context: <a href=3D"http://apache-ignite-users.70518.x=
6.nabble.com/setting-query-timeout-and-getting-partial-result-instead-of-ex=
ception-tp12266.html" rel=3D"noreferrer" target=3D"_blank">http://apache-ig=
nite-users.<wbr>70518.x6.nabble.com/setting-<wbr>query-timeout-and-getting-=
<wbr>partial-result-instead-of-<wbr>exception-tp12266.html</a><br>
Sent from the Apache Ignite Users mailing list archive at Nabble.com.<br>
</blockquote></div><br><br clear=3D"all"><div><br></div>-- <br><div class=
=3D"gmail_signature" data-smartmail=3D"gmail_signature"><div dir=3D"ltr"><d=
iv>Best regards,<br>Andrey V. Mashenkov<br></div></div></div>
</div>

--f403045f8d022b7cea054e1217bf--