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 entries are very large. What does the data look like? [1] https://issues.apache.org/jira/browse/IGNITE-13635 On Wed, Oct 28, 2020 at 1:43 PM Ravi Makwana <[email protected]> wrote: > 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 <[email protected]> wrote: > >> 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 project properties. >> >> On Wed, Oct 28, 2020 at 1:06 PM Ravi Makwana <[email protected]> >> wrote: >> >>> Hi Pavel, >>> >>> Thanks for the information. >>> >>> We have noticed our service is taking max 2GB memory which is noticed in >>> task manager and stopping app pool at same time server memory utilization >>> is 80% so we have still memory spare 20%. >>> >>> Still we are not able to correlate the issue, I would like to share some >>> more logs. Could you suggest what is happening at the moment? >>> >>> Thanks, >>> >>>
