You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by Ajay <aj...@6dtech.co.in> on 2017/05/15 08:00:38 UTC
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
<property name="memoryConfiguration">
<bean class="org.apache.ignite.configuration.MemoryConfiguration">
<property name="defaultMemoryPolicyName" value="Default_Region" />
<property name="pageSize" value="4096" />
<property name="systemCacheInitialSize" value="#{40 * 1024 * 1024}" />
<property name="systemCacheMaxSize" value="#{40 * 1024 * 1024}" />
<property name="memoryPolicies">
<list>
<bean class="org.apache.ignite.configuration.MemoryPolicyConfiguration">
<property name="name" value="Default_Region" />
<property name="initialSize" value="#{4L * 1024 * 1024 * 1024}" />
<property name="maxSize" value="#{6L * 1024 * 1024 * 1024}" />
<property name="pageEvictionMode" value="RANDOM_2_LRU" />
<property name="evictionThreshold" value="0.6" />
<property name="metricsEnabled" value="true" />
</bean>
</list>
</property>
</bean>
</property>
and i am facing issue
java.lang.IllegalArgumentException
at sun.misc.Unsafe.allocateMemory(Native Method)
at
org.apache.ignite.internal.util.GridUnsafe.allocateMemory(GridUnsafe.java:1054)
is issue with configuration or ignite?
Thanks
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite2-0-memory-policy-limit-tp12840.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: Ignite2.0 memory policy limit
Posted by Alexey Goncharuk <al...@gmail.com>.
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 <dm...@gridgain.com>:
> Alex, thanks.
>
> Can the ticket be resolved in 2.1?
>
>
> On Wednesday, May 17, 2017, Alexey Goncharuk <al...@gmail.com>
> 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 <se...@gmail.com>:
>>
>>> 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 <
>>> andrey.mashenkov@gmail.com> 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 <aj...@6dtech.co.in> 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
>>>>
>>>
>>>
>>
Re: Ignite2.0 memory policy limit
Posted by Denis Magda <dm...@gridgain.com>.
Alex, thanks.
Can the ticket be resolved in 2.1?
On Wednesday, May 17, 2017, Alexey Goncharuk <al...@gmail.com>
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 <sergey.chugunov@gmail.com
> <javascript:_e(%7B%7D,'cvml','sergey.chugunov@gmail.com');>>:
>
>> 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 <
>> andrey.mashenkov@gmail.com
>> <javascript:_e(%7B%7D,'cvml','andrey.mashenkov@gmail.com');>> 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 <ajay.babu@6dtech.co.in
>>> <javascript:_e(%7B%7D,'cvml','ajay.babu@6dtech.co.in');>> 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
>>>
>>
>>
>
Re: Ignite2.0 memory policy limit
Posted by Alexey Goncharuk <al...@gmail.com>.
Created a follow-up UX ticket:
https://issues.apache.org/jira/browse/IGNITE-5248
2017-05-17 19:20 GMT+03:00 Sergey Chugunov <se...@gmail.com>:
> 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 <
> andrey.mashenkov@gmail.com> 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 <aj...@6dtech.co.in> 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
>>
>
>
Re: Ignite2.0 memory policy limit
Posted by Sergey Chugunov <se...@gmail.com>.
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 <
andrey.mashenkov@gmail.com> 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 <aj...@6dtech.co.in> 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
>
Re: Ignite2.0 memory policy limit
Posted by Andrey Mashenkov <an...@gmail.com>.
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 <aj...@6dtech.co.in> 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.
> 70518.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
Re: Ignite2.0 memory policy limit
Posted by Ajay <aj...@6dtech.co.in>.
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.70518.x6.nabble.com/Ignite2-0-memory-policy-limit-tp12840p12958.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: Ignite2.0 memory policy limit
Posted by Denis Magda <dm...@apache.org>.
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 name and version? The logs don’t say it.
Did you try to start the node using the same config on another machine?
—
Denis
> On May 15, 2017, at 11:29 PM, Ajay <aj...@6dtech.co.in> wrote:
>
> HI Denis,
>
> Please find requested data
>
> ignite_server_config.xml
> <http://apache-ignite-users.70518.x6.nabble.com/file/n12875/ignite_server_config.xml>
> ignite-c88d9d24.log
> <http://apache-ignite-users.70518.x6.nabble.com/file/n12875/ignite-c88d9d24.log>
>
> OS and Java version you can get by log file and total RAM size in was 32 GB.
>
>
> Thanks
>
>
>
>
>
> --
> View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite2-0-memory-policy-limit-tp12840p12875.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: Ignite2.0 memory policy limit
Posted by Ajay <aj...@6dtech.co.in>.
HI Denis,
Please find requested data
ignite_server_config.xml
<http://apache-ignite-users.70518.x6.nabble.com/file/n12875/ignite_server_config.xml>
ignite-c88d9d24.log
<http://apache-ignite-users.70518.x6.nabble.com/file/n12875/ignite-c88d9d24.log>
OS and Java version you can get by log file and total RAM size in was 32 GB.
Thanks
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite2-0-memory-policy-limit-tp12840p12875.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: Ignite2.0 memory policy limit
Posted by Denis Magda <dm...@apache.org>.
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 configuration you use. Plus tell how much RAM you have in total and what’re Java and Windows versions.
—
Denis
> On May 15, 2017, at 8:32 AM, Ajay <aj...@6dtech.co.in> wrote:
>
> [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
> org.apache.ignite.internal.util.GridUnsafe.allocateMemory(GridUnsafe.java:1054)
> at
> org.apache.ignite.internal.mem.unsafe.UnsafeMemoryProvider.nextRegion(UnsafeMemoryProvider.java:76)
> at
> org.apache.ignite.internal.pagemem.impl.PageMemoryNoStoreImpl.addSegment(PageMemoryNoStoreImpl.java:616)
> at
> org.apache.ignite.internal.pagemem.impl.PageMemoryNoStoreImpl.start(PageMemoryNoStoreImpl.java:222)
> at
> org.apache.ignite.internal.processors.cache.database.IgniteCacheDatabaseSharedManager.startMemoryPolicies(IgniteCacheDatabaseSharedManager.java:202)
> at
> org.apache.ignite.internal.processors.cache.database.IgniteCacheDatabaseSharedManager.init(IgniteCacheDatabaseSharedManager.java:119)
> at
> org.apache.ignite.internal.processors.cache.database.IgniteCacheDatabaseSharedManager.start0(IgniteCacheDatabaseSharedManager.java:98)
> at
> org.apache.ignite.internal.processors.cache.GridCacheSharedManagerAdapter.start(GridCacheSharedManagerAdapter.java:53)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.start(GridCacheProcessor.java:643)
> at
> org.apache.ignite.internal.IgniteKernal.startProcessor(IgniteKernal.java:1763)
> at
> org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:925)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1895)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1647)
> at
> org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1075)
> at
> org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:993)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:879)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:778)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:648)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:617)
> at org.apache.ignite.Ignition.start(Ignition.java:347)
> at
> org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:302)
> [20:45:42,735][ERROR][main][IgniteKernal] Got exception while starting
> (will rollback startup routine).
> java.lang.IllegalArgumentException
> at sun.misc.Unsafe.allocateMemory(Native Method)
> at
> org.apache.ignite.internal.util.GridUnsafe.allocateMemory(GridUnsafe.java:1054)
> at
> org.apache.ignite.internal.mem.unsafe.UnsafeMemoryProvider.nextRegion(UnsafeMemoryProvider.java:76)
> at
> org.apache.ignite.internal.pagemem.impl.PageMemoryNoStoreImpl.addSegment(PageMemoryNoStoreImpl.java:616)
> at
> org.apache.ignite.internal.pagemem.impl.PageMemoryNoStoreImpl.start(PageMemoryNoStoreImpl.java:222)
> at
> org.apache.ignite.internal.processors.cache.database.IgniteCacheDatabaseSharedManager.startMemoryPolicies(IgniteCacheDatabaseSharedManager.java:202)
> at
> org.apache.ignite.internal.processors.cache.database.IgniteCacheDatabaseSharedManager.init(IgniteCacheDatabaseSharedManager.java:119)
> at
> org.apache.ignite.internal.processors.cache.database.IgniteCacheDatabaseSharedManager.start0(IgniteCacheDatabaseSharedManager.java:98)
> at
> org.apache.ignite.internal.processors.cache.GridCacheSharedManagerAdapter.start(GridCacheSharedManagerAdapter.java:53)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.start(GridCacheProcessor.java:643)
> at
> org.apache.ignite.internal.IgniteKernal.startProcessor(IgniteKernal.java:1763)
> at
> org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:925)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1895)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1647)
> at
> org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1075)
> at
> org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:993)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:879)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:778)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:648)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:617)
> at org.apache.ignite.Ignition.start(Ignition.java:347)
> at
> org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:302)
> [20:45:42,737][WARN ][main][IgniteKernal] Attempt to stop starting grid.
> This operation cannot be guaranteed to be successful.
>
>
>
>
> --
> View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite2-0-memory-policy-limit-tp12840p12855.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: Ignite2.0 memory policy limit
Posted by Ajay <aj...@6dtech.co.in>.
[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
org.apache.ignite.internal.util.GridUnsafe.allocateMemory(GridUnsafe.java:1054)
at
org.apache.ignite.internal.mem.unsafe.UnsafeMemoryProvider.nextRegion(UnsafeMemoryProvider.java:76)
at
org.apache.ignite.internal.pagemem.impl.PageMemoryNoStoreImpl.addSegment(PageMemoryNoStoreImpl.java:616)
at
org.apache.ignite.internal.pagemem.impl.PageMemoryNoStoreImpl.start(PageMemoryNoStoreImpl.java:222)
at
org.apache.ignite.internal.processors.cache.database.IgniteCacheDatabaseSharedManager.startMemoryPolicies(IgniteCacheDatabaseSharedManager.java:202)
at
org.apache.ignite.internal.processors.cache.database.IgniteCacheDatabaseSharedManager.init(IgniteCacheDatabaseSharedManager.java:119)
at
org.apache.ignite.internal.processors.cache.database.IgniteCacheDatabaseSharedManager.start0(IgniteCacheDatabaseSharedManager.java:98)
at
org.apache.ignite.internal.processors.cache.GridCacheSharedManagerAdapter.start(GridCacheSharedManagerAdapter.java:53)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.start(GridCacheProcessor.java:643)
at
org.apache.ignite.internal.IgniteKernal.startProcessor(IgniteKernal.java:1763)
at
org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:925)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1895)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1647)
at
org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1075)
at
org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:993)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:879)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:778)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:648)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:617)
at org.apache.ignite.Ignition.start(Ignition.java:347)
at
org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:302)
[20:45:42,735][ERROR][main][IgniteKernal] Got exception while starting
(will rollback startup routine).
java.lang.IllegalArgumentException
at sun.misc.Unsafe.allocateMemory(Native Method)
at
org.apache.ignite.internal.util.GridUnsafe.allocateMemory(GridUnsafe.java:1054)
at
org.apache.ignite.internal.mem.unsafe.UnsafeMemoryProvider.nextRegion(UnsafeMemoryProvider.java:76)
at
org.apache.ignite.internal.pagemem.impl.PageMemoryNoStoreImpl.addSegment(PageMemoryNoStoreImpl.java:616)
at
org.apache.ignite.internal.pagemem.impl.PageMemoryNoStoreImpl.start(PageMemoryNoStoreImpl.java:222)
at
org.apache.ignite.internal.processors.cache.database.IgniteCacheDatabaseSharedManager.startMemoryPolicies(IgniteCacheDatabaseSharedManager.java:202)
at
org.apache.ignite.internal.processors.cache.database.IgniteCacheDatabaseSharedManager.init(IgniteCacheDatabaseSharedManager.java:119)
at
org.apache.ignite.internal.processors.cache.database.IgniteCacheDatabaseSharedManager.start0(IgniteCacheDatabaseSharedManager.java:98)
at
org.apache.ignite.internal.processors.cache.GridCacheSharedManagerAdapter.start(GridCacheSharedManagerAdapter.java:53)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.start(GridCacheProcessor.java:643)
at
org.apache.ignite.internal.IgniteKernal.startProcessor(IgniteKernal.java:1763)
at
org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:925)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1895)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1647)
at
org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1075)
at
org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:993)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:879)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:778)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:648)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:617)
at org.apache.ignite.Ignition.start(Ignition.java:347)
at
org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:302)
[20:45:42,737][WARN ][main][IgniteKernal] Attempt to stop starting grid.
This operation cannot be guaranteed to be successful.
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite2-0-memory-policy-limit-tp12840p12855.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: Ignite2.0 memory policy limit
Posted by Andrey Mashenkov <an...@gmail.com>.
Hi Ajay,
Would you please share a full stacktrace?
On Mon, May 15, 2017 at 11:00 AM, Ajay <aj...@6dtech.co.in> wrote:
> Hi,
>
> Is Ignite having any limit to create the memory region on single server
> node. Because i created server node with following
>
> <property name="memoryConfiguration">
> <bean class="org.apache.ignite.configuration.MemoryConfiguration">
> <property name="defaultMemoryPolicyName"
> value="Default_Region" />
> <property name="pageSize" value="4096" />
> <property name="systemCacheInitialSize" value="#{40 * 1024
> * 1024}" />
> <property name="systemCacheMaxSize" value="#{40 * 1024 *
> 1024}" />
> <property name="memoryPolicies">
> <list>
> <bean class="org.apache.ignite.
> configuration.MemoryPolicyConfiguration">
> <property name="name"
> value="Default_Region" />
> <property name="initialSize"
> value="#{4L * 1024 * 1024 * 1024}" />
> <property name="maxSize"
> value="#{6L * 1024 * 1024 * 1024}" />
> <property name="pageEvictionMode"
> value="RANDOM_2_LRU" />
> <property name="evictionThreshold"
> value="0.6" />
> <property name="metricsEnabled"
> value="true" />
> </bean>
> </list>
> </property>
> </bean>
> </property>
>
> and i am facing issue
> java.lang.IllegalArgumentException
> at sun.misc.Unsafe.allocateMemory(Native Method)
> at
> org.apache.ignite.internal.util.GridUnsafe.allocateMemory(GridUnsafe.
> java:1054)
>
> is issue with configuration or ignite?
>
> Thanks
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/Ignite2-0-memory-policy-limit-tp12840.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>
--
Best regards,
Andrey V. Mashenkov