ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "vinay (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-5926) Puts on near cache hangs
Date Fri, 04 Aug 2017 19:12:00 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-5926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16114848#comment-16114848

vinay commented on IGNITE-5926:

This is just a thought that near caches will mostly have very frequent evictions considering
their small size (as compared to server cache) and considering cases where client is performing
a lot of reads or writes. This may significantly increase communications between client and
server. I don't have much knowledge on internal working / implementation of ignite but there
may be more complexities in this approach when we consider cases like node failures. 
I think there may be some better approach to solve this problem than sending communication
from client on each eviction and making server aware of each eviction on near caches. 

> Puts on near cache hangs
> ------------------------
>                 Key: IGNITE-5926
>                 URL: https://issues.apache.org/jira/browse/IGNITE-5926
>             Project: Ignite
>          Issue Type: Bug
>    Affects Versions: 2.0, 2.1
>            Reporter: vinay
>             Fix For: 2.2
>         Attachments: IgniteNearCacheProblem.java
> Cache puts on near cache on client node hangs after putting same number of keys (if keys
and values are same during test). Most probably problem occurs when cache on server reaches
max memory and starts page eviction. *Attaching java class with main method to reproduce problem*.
If near cache is not used then the same test works fine.
> Steps to reproduce
> # Start a server node with one memory region with max size 100 MB. Page Evction Strategy
as RANDOM_LRU. Set this memory region as default. Create a REPLICATED cache as part of server's
> # Start a client node and create a near cache for the cache created on server. Keep near
cache init size and max size 1000 with eviction policy LRU.
> # Start a infinite while loop to put objects in near cache.

This message was sent by Atlassian JIRA

View raw message