Re: IgniteOutOfMemoryException in LOCAL cache mode with persistence enabled

2019-12-11 Thread Sergey Chugunov
om: user@ignite.apache.org At: 12/10/19 11:24:35 >> To: Mitchell Rathbun (BLOOMBERG/ 731 LEX ) , >> user@ignite.apache.org >> Subject: Re: IgniteOutOfMemoryException in LOCAL cache mode with >> persistence enabled >> >> Hello! >> >> 10M is very very l

Re: IgniteOutOfMemoryException in LOCAL cache mode with persistence enabled

2019-12-11 Thread Denis Magda
hy this might be would be appreciated. > > From: user@ignite.apache.org At: 12/10/19 11:24:35 > To: Mitchell Rathbun (BLOOMBERG/ 731 LEX ) , > user@ignite.apache.org > Subject: Re: IgniteOutOfMemoryException in LOCAL cache mode with > persistence enabled > > Hello! > > 10M

Re: IgniteOutOfMemoryException in LOCAL cache mode with persistence enabled

2019-12-11 Thread Ilya Kasnacheev
y this might be would be appreciated. > > From: user@ignite.apache.org At: 12/10/19 11:24:35 > To: Mitchell Rathbun (BLOOMBERG/ 731 LEX ) , > user@ignite.apache.org > Subject: Re: IgniteOutOfMemoryException in LOCAL cache mode with > persistence enabled > > Hello! > > 10M is

Re: IgniteOutOfMemoryException in LOCAL cache mode with persistence enabled

2019-12-10 Thread Mitchell Rathbun (BLOOMBERG/ 731 LEX)
) , user@ignite.apache.org Subject: Re: IgniteOutOfMemoryException in LOCAL cache mode with persistence enabled Hello! 10M is very very low-ball for testing performance of disk, considering how Ignite's wal/checkpoints are structured. As already told, it does not even work properly. I rec

Re: IgniteOutOfMemoryException in LOCAL cache mode with persistence enabled

2019-12-10 Thread Ilya Kasnacheev
ectory does not seem to have any logs > > From: user@ignite.apache.org At: 12/03/19 19:00:18 > To: user@ignite.apache.org > Subject: Re: IgniteOutOfMemoryException in LOCAL cache mode with > persistence enabled > > For our configuration properties, our DataRegion initi

Re: IgniteOutOfMemoryException in LOCAL cache mode with persistence enabled

2019-12-03 Thread Mitchell Rathbun (BLOOMBERG/ 731 LEX)
: IgniteOutOfMemoryException in LOCAL cache mode with persistence enabled For our configuration properties, our DataRegion initialSize and MaxSize was set to 11 MB and persistence was enabled. For DataStorage, our pageSize was set to 8192 instead of 4096. For Cache, write behind is disabled, on

Re: IgniteOutOfMemoryException in LOCAL cache mode with persistence enabled

2019-12-03 Thread Mitchell Rathbun (BLOOMBERG/ 731 LEX)
@ignite.apache.org At: 12/03/19 13:40:32To: user@ignite.apache.org Subject: Re: IgniteOutOfMemoryException in LOCAL cache mode with persistence enabled Hi Mitchell, Looks like it could be easily reproduced on low off-heap sizes, I tried with simple puts and got the same exception: class

Re: IgniteOutOfMemoryException in LOCAL cache mode with persistence enabled

2019-12-03 Thread akurbanov
Hi Mitchell, Looks like it could be easily reproduced on low off-heap sizes, I tried with simple puts and got the same exception: class org.apache.ignite.internal.mem.IgniteOutOfMemoryException: Failed to find a page for eviction [segmentCapacity=1580, loaded=619, maxDirtyPages=465, dirtyPages=61

IgniteOutOfMemoryException in LOCAL cache mode with persistence enabled

2019-12-03 Thread Mitchell Rathbun (BLOOMBERG/ 731 LEX)
We are running Ignite in LOCAL mode currently and have persistence enabled. For this specific test, the off heap memory was set to as low as possible (~10 MB) to test on-disk performance. We have multiple caches sharing the same DataRegion. For the test, we basically write synchronously to cache