Re: Ignite Client Node Stopped With Out Of Memory

2020-10-28 Thread Pavel Tupitsyn
On of these, depending on your query type: * new ScanQuery() { PageSize = 5 } * new SqlQuery() { PageSize = 5 } On Wed, Oct 28, 2020 at 5:24 PM Ravi Makwana wrote: > Hi Paval, > > As we are not setting explicitly QueryBase.Pagesize for SqlQuery and > SqlFieldQuery so default will be used as

Re: Ignite Client Node Stopped With Out Of Memory

2020-10-28 Thread Ravi Makwana
Hi Paval, As we are not setting explicitly QueryBase.Pagesize for SqlQuery and SqlFieldQuery so default will be used as 1024. We have not found so far any example by looking the same we can try to explicitly set the Query base.Pagesize. Can we have any reference by checking that we can try to

Re: Ignite Client Node Stopped With Out Of Memory

2020-10-28 Thread Ravi Makwana
On Wed, 28 Oct, 2020, 5:55 pm Pavel Tupitsyn, wrote: > I found a bug in Ignite [1] which probably causes the issue on your side. > > Looks like you are running a query (is it a ScanQuery or SqlQuery?) and > the size of one results page exceeds 2GB. > Please try using a smaller value for

Re: Ignite Client Node Stopped With Out Of Memory

2020-10-28 Thread Pavel Tupitsyn
I found a bug in Ignite [1] which probably causes the issue on your side. Looks like you are running a query (is it a ScanQuery or SqlQuery?) and the size of one results page exceeds 2GB. Please try using a smaller value for *QueryBase.PageSize*. If you use the default value of 1024, your cache

Re: Ignite Client Node Stopped With Out Of Memory

2020-10-28 Thread Ravi Makwana
Hi, Our service is running with 64 bit and we have verified the same in our app server too. Any finding from the logs? Is there any way to replicate it? Thanks, On Wed, 28 Oct 2020 at 15:47, Pavel Tupitsyn wrote: > Looks like the app is running in 32 bit mode, which can't use more than >

Re: Ignite Client Node Stopped With Out Of Memory

2020-10-28 Thread Pavel Tupitsyn
Looks like the app is running in 32 bit mode, which can't use more than 2GB of memory. JVM and memory regions pre-allocate all of it, leaving nothing for .NET to use. Please check the `Platform` column in the Task Manager - does it say `32 bit`? If yes, then try disabling `Prefer 32 bit` in the

Re: Ignite Client Node Stopped With Out Of Memory

2020-10-25 Thread Pavel Tupitsyn
Hi Ravi, The exception indicates that Ignite.NET failed to allocate unmanaged memory on .NET side while trying to pass query data from Java to .NET. This indicates that your system has run out of memory. Possible reasons are: * Memory is consumed by other apps * Memory is consumed by this app *