Re: Ignite2.0 memory policy limit

It's pretty simple. I've added newbie label for it, anyone can pick it up. 2017-05-17 21:03 GMT+03:00 Denis Magda : > Alex, thanks. > > Can the ticket be resolved in 2.1? > > > On Wednesday, May 17, 2017, Alexey Goncharuk > wrote: > >> Created a

Re: Ignite2.0 memory policy limit

Alex, thanks. Can the ticket be resolved in 2.1? On Wednesday, May 17, 2017, Alexey Goncharuk wrote: > Created a follow-up UX ticket: https://issues.apache. > org/jira/browse/IGNITE-5248 > > 2017-05-17 19:20 GMT+03:00 Sergey Chugunov

Re: Ignite2.0 memory policy limit

Created a follow-up UX ticket: https://issues.apache.org/jira/browse/IGNITE-5248 2017-05-17 19:20 GMT+03:00 Sergey Chugunov : > 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

Re: Ignite2.0 memory policy limit

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

Re: Ignite2.0 memory policy limit

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

Re: Ignite2.0 memory policy limit

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

Re: Ignite2.0 memory policy limit

Ajay, I could successfully start a node using your configuration on my laptop. Could you check how many processes are running on your Linux machine and how much physical RAM is left for the Ignite process? You can share the output of “top” or similar tool. Btw, what’s the Linux distribution

Re: Ignite2.0 memory policy limit

HI Denis, Please find requested data ignite_server_config.xml ignite-c88d9d24.log OS and Java version you can get by log

Re: Ignite2.0 memory policy limit

Alex G., please look at this discussion. I don’t think that IAE is thrown as a result of insufficient RAM on the machine. Everything works perfectly fine on my Mac OS laptop even when a region with initial size > total RAM available is requested. Ajay, share a complete log file and

Re: Ignite2.0 memory policy limit

[20:45:42,727][ERROR][main][IgniteKernal] Exception during start processors, node will be stopped and close connections java.lang.IllegalArgumentException at sun.misc.Unsafe.allocateMemory(Native Method) at

Re: Ignite2.0 memory policy limit

Hi Ajay, Would you please share a full stacktrace? On Mon, May 15, 2017 at 11:00 AM, Ajay wrote: > Hi, > > Is Ignite having any limit to create the memory region on single server > node. Because i created server node with following > > > >

Ignite2.0 memory policy limit

Hi, Is Ignite having any limit to create the memory region on single server node. Because i created server node with following