Created a follow-up UX ticket: https://issues.apache.org/jira/browse/IGNITE-5248
2017-05-17 19:20 GMT+03:00 Sergey Chugunov <[email protected]>: > Ajay, > > I managed to reproduce your issue. As I can see from logs you're starting > Ignite using 32-bit JVM. > > To fix your issue just use 64-bit JVM or decrease initial/maxSize settings > in memory configuration to something below 3 Gigs. > > Thanks, > Sergey. > > > > > > On Wed, May 17, 2017 at 6:40 PM, Andrey Mashenkov < > [email protected]> wrote: > >> Hi Ajay, >> >> Ignite allocate memory by chunks. The first chunk is allocating on Ignite >> start and its size equal to initialSize. Other chunks allocated on demand >> and its size <=256M. >> Seems, your system can't allocate 4Gb memory as single chunk. >> >> What is /proc/sys/vm/overcommit_memory value? Try to set it to '1' if it >> differs. >> >> >> On Wed, May 17, 2017 at 10:09 AM, Ajay <[email protected]> wrote: >> >>> Hi Denis, >>> >>> Please find "top" snapshot. >>> >>> >>> top - 12:23:56 up 31 days, 20:28, 5 users, load average: 10.60, 9.40, >>> 7.31 >>> Tasks: 406 total, 1 running, 405 sleeping, 0 stopped, 0 zombie >>> Cpu(s): 42.1%us, 2.2%sy, 0.0%ni, 53.2%id, 2.2%wa, 0.0%hi, 0.4%si, >>> 0.0%st >>> Mem: 32865584k total, 31864932k used, 1000652k free, 520060k buffers >>> Swap: 16383996k total, 45400k used, 16338596k free, 21417052k cached >>> >>> >>> Thanks >>> >>> >>> >>> -- >>> View this message in context: http://apache-ignite-users.705 >>> 18.x6.nabble.com/Ignite2-0-memory-policy-limit-tp12840p12958.html >>> Sent from the Apache Ignite Users mailing list archive at Nabble.com. >>> >> >> >> >> -- >> Best regards, >> Andrey V. Mashenkov >> > >
