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: <1479243682671-9007.post@n6.nabble.com>
References: <CALPm_-DJh3zpDWfd1JtXyZMVj9-ARgP4Yd3iNMyY3FWszXgniQ@mail.gmail.com>
 <1479243682671-9007.post@n6.nabble.com>
From: Anil <anilklce@gmail.com>
Date: Wed, 30 Nov 2016 11:13:00 +0530
Message-ID: <CALPm_-ALHMMdYNfELGJ3PZp46UcxspOrdSDM-9FCe1EccQQXjA@mail.gmail.com>
Subject: Re: Limit the number of results query
To: user@ignite.apache.org
Content-Type: multipart/alternative; boundary=001a11474ba4f3c03605427e2fb3
archived-at: Wed, 30 Nov 2016 05:43:48 -0000

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

HI Val,

thanks for response.

OOO is on server. Does server have separate memory blocks for each query
results ? how does that work when number of number of queries executed in
parallel ?

Thanks

On 16 November 2016 at 02:31, vkulichenko <valentin.kulichenko@gmail.com>
wrote:

> Do you mean OOM on the server or on the client? On server you indeed will
> need some spare space for any ongoing operations (not only queries,
> actually). You should make sure that this space is enough for you load. On
> client you should not get OOM because results are sent in pages (unless you
> call QueryCursor.getAll). If you iterate through the cursor, you will have
> only one page in client memory at a time which is 1024 rows by default.
>
> Query cancellation and timeout will be available in 1.8:
> https://issues.apache.org/jira/browse/IGNITE-2680
>
> -Val
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/Limit-the-number-of-results-query-tp9002p9007.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>

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

<div dir=3D"ltr">HI Val,<div><br></div><div>thanks for response.</div><div>=
<br></div><div>OOO is on server. Does server have separate memory blocks fo=
r each query results ? how does that work when number of number of queries =
executed in parallel ?=C2=A0</div><div><br></div><div>Thanks</div></div><di=
v class=3D"gmail_extra"><br><div class=3D"gmail_quote">On 16 November 2016 =
at 02:31, vkulichenko <span dir=3D"ltr">&lt;<a href=3D"mailto:valentin.kuli=
chenko@gmail.com" target=3D"_blank">valentin.kulichenko@gmail.com</a>&gt;</=
span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8e=
x;border-left:1px #ccc solid;padding-left:1ex">Do you mean OOM on the serve=
r or on the client? On server you indeed will<br>
need some spare space for any ongoing operations (not only queries,<br>
actually). You should make sure that this space is enough for you load. On<=
br>
client you should not get OOM because results are sent in pages (unless you=
<br>
call QueryCursor.getAll). If you iterate through the cursor, you will have<=
br>
only one page in client memory at a time which is 1024 rows by default.<br>
<br>
Query cancellation and timeout will be available in 1.8:<br>
<a href=3D"https://issues.apache.org/jira/browse/IGNITE-2680" rel=3D"norefe=
rrer" target=3D"_blank">https://issues.apache.org/<wbr>jira/browse/IGNITE-2=
680</a><br>
<br>
-Val<br>
<br>
<br>
<br>
--<br>
View this message in context: <a href=3D"http://apache-ignite-users.70518.x=
6.nabble.com/Limit-the-number-of-results-query-tp9002p9007.html" rel=3D"nor=
eferrer" target=3D"_blank">http://apache-ignite-users.<wbr>70518.x6.nabble.=
com/Limit-the-<wbr>number-of-results-query-<wbr>tp9002p9007.html</a><br>
Sent from the Apache Ignite Users mailing list archive at Nabble.com.<br>
</blockquote></div><br></div>

--001a11474ba4f3c03605427e2fb3--