Re: [MSG Uncertified] Re: Ignite fails to allocate more memory then initially allocated when maxSize property provided in MemoryPolicyConfiguration

[Siarhei Mironchyk]

Thanks for response. Yes, I tried to reproduce in latest Ignite 2.1 and all
works good.

Sorry, forgot to specify version. If that an issue it is in ver.
2.0.0#20170430-sha1:d4eef3c6
Other system information:
Config URL:
file:/C:/work/apache-ignite/apache-ignite-fabric-2.0.0-bin/examples/config/my-client-example-memory-policies.xml
OS: Windows 7 6.1 amd64
Language runtime: Java Platform API Specification ver. 1.8
VM information: Java(TM) SE Runtime Environment 1.8.0_121-b13 Oracle
Corporation Java HotSpot(TM) 64-Bit Server VM 25.121-b13
VM total memory: 5.3GB



On Thu, Aug 10, 2017 at 8:47 PM, afedotov 
wrote:

> Hi,
>
> Provided configuration works as expected on Ignite version 2.1.
> On my side, in this configuration, I got 3 memory segment allocations.
>
> Have you tried requesting cache.size() after populating the cache?
> Please provide the full configuration files so as I could check them.
>
> Kind regards,
> Alex.
>
> On Thu, Aug 10, 2017 at 6:58 PM, smironchyk [via Apache Ignite Users] <[hidden
> email] <http:///user/SendEmail.jtp?type=node&node=16105&i=0>> wrote:
>
>> Hi! I am trying to configure and test my custom memory policy for the
>> simple 1 client - 1 server node topology.
>>
>> In order to do this I added memory configuration for my server node like
>> this with 1GB_Region_Eviction memory policy configured.
>>
>> 
>> 
>>
>> 
>>
>> 
>> 
>> 
>> > value="1GB_Region_Eviction"/>
>> > />
>> 
>> 
>> > value="RANDOM_2_LRU"/>
>> 
>>
>> 
>> 
>> 
>> 
>>
>> My client node connects to server and starts putting new entries with
>> size ~ 2MB to cache with interval in 1 sec. See client config below.
>> 
>> 
>>
>> 
>>
>> 
>> 
>> 
>> 
>> 
>> 
>> > value="1GB_Region_Eviction"/>
>>
>> > value="FULL_SYNC"/>
>> 
>> 
>> 
>> > factory-method="factoryOf">
>> 
>> 
>> 
>> 
>> 
>> 
>> ...
>> 
>>
>> I've got message in server node log like this
>> [12:34:16,622][INFO][sys-stripe-1-#2%null%][PageMemoryNoStoreImpl]
>> Allocated next memory segment [plcName=1GB_Region_Eviction, chunkSize=268.4
>> MB]
>> And after this no more memory chunks allocated by node. And my maxSize
>> ignored by cache.
>> What am I doing wrong here. Please advise.
>>
>> my-client-example-memory-policies.xml
>> <http://apache-ignite-users.70518.x6.nabble.com/file/n16101/my-client-example-memory-policies.xml>
>> my-example-memory-policies.xml
>> <http://apache-ignite-users.70518.x6.nabble.com/file/n16101/my-example-memory-policies.xml>
>> MyMemoryPoliciesExample.java
>> <http://apache-ignite-users.70518.x6.nabble.com/file/n16101/MyMemoryPoliciesExample.java>
>>
>> --
>> If you reply to this email, your message will be added to the discussion
>> below:
>> http://apache-ignite-users.70518.x6.nabble.com/Ignite-fails-
>> to-allocate-more-memory-then-initially-allocated-when-maxSi
>> ze-property-provided-in-Memon-tp16101.html
>> To start a new topic under Apache Ignite Users, email [hidden email]
>> <http:///user/SendEmail.jtp?type=node&node=16105&i=1>
>> To unsubscribe from Apache Ignite Users, click here.
>> NAML
>> <http://apache-ignite-users.70518.x6.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>>
>
>
> --
> View this message in context: Re: Ignite fails to allocate more memory
> then initially allocated when maxSize property provided in
&g

Re: Ignite fails to allocate more memory then initially allocated when maxSize property provided in MemoryPolicyConfiguration

[afedotov]

Hi,

Provided configuration works as expected on Ignite version 2.1.
On my side, in this configuration, I got 3 memory segment allocations.

Have you tried requesting cache.size() after populating the cache?
Please provide the full configuration files so as I could check them.

Kind regards,
Alex.

On Thu, Aug 10, 2017 at 6:58 PM, smironchyk [via Apache Ignite Users] <
ml+s70518n16101...@n6.nabble.com> wrote:

> Hi! I am trying to configure and test my custom memory policy for the
> simple 1 client - 1 server node topology.
>
> In order to do this I added memory configuration for my server node like
> this with 1GB_Region_Eviction memory policy configured.
>
> 
> 
>
> 
>
> 
> 
> 
>  value="1GB_Region_Eviction"/>
> 
> 
> 
>  value="RANDOM_2_LRU"/>
> 
>
> 
> 
> 
> 
>
> My client node connects to server and starts putting new entries with size
> ~ 2MB to cache with interval in 1 sec. See client config below.
> 
> 
>
> 
>
> 
> 
> 
> 
> 
> 
>  value="1GB_Region_Eviction"/>
>
>  value="FULL_SYNC"/>
> 
> 
> 
>  factory-method="factoryOf">
> 
> 
> 
> 
> 
> 
> ...
> 
>
> I've got message in server node log like this
> [12:34:16,622][INFO][sys-stripe-1-#2%null%][PageMemoryNoStoreImpl]
> Allocated next memory segment [plcName=1GB_Region_Eviction, chunkSize=268.4
> MB]
> And after this no more memory chunks allocated by node. And my maxSize
> ignored by cache.
> What am I doing wrong here. Please advise.
>
> my-client-example-memory-policies.xml
> 
> my-example-memory-policies.xml
> 
> MyMemoryPoliciesExample.java
> 
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
> http://apache-ignite-users.70518.x6.nabble.com/Ignite-
> fails-to-allocate-more-memory-then-initially-allocated-when-
> maxSize-property-provided-in-Memon-tp16101.html
> To start a new topic under Apache Ignite Users, email
> ml+s70518n1...@n6.nabble.com
> To unsubscribe from Apache Ignite Users, click here
> 
> .
> NAML
> 
>




--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Ignite-fails-to-allocate-more-memory-then-initially-allocated-when-maxSize-property-provided-in-Memon-tp16101p16105.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Ignite fails to allocate more memory then initially allocated when maxSize property provided in MemoryPolicyConfiguration

[smironchyk]

Hi! I am trying to configure and test my custom memory policy for the simple
1 client - 1 server node topology.

In order to do this I added memory configuration for my server node like
this with 1GB_Region_Eviction memory policy configured.





















My client node connects to server and starts putting new entries with size ~
2MB to cache with interval in 1 sec. See client config below.
























...
 

I've got message in server node log like this
[12:34:16,622][INFO][sys-stripe-1-#2%null%][PageMemoryNoStoreImpl] Allocated
next memory segment [plcName=1GB_Region_Eviction, chunkSize=268.4 MB]
And after this no more memory chunks allocated by node. And my maxSize
ignored by cache.
What am I doing wrong here. Please advise.

my-client-example-memory-policies.xml

  
my-example-memory-policies.xml

  
MyMemoryPoliciesExample.java

  



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Ignite-fails-to-allocate-more-memory-then-initially-allocated-when-maxSize-property-provided-in-Memon-tp16101.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.