You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "nabarun (JIRA)" <ji...@apache.org> on 2016/11/17 19:21:59 UTC

[jira] [Updated] (GEODE-2122) Receiver still accepts put when it is low on memory

     [ https://issues.apache.org/jira/browse/GEODE-2122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

nabarun updated GEODE-2122:
---------------------------
    Component/s: wan

> Receiver still accepts put when it is low on memory 
> ----------------------------------------------------
>
>                 Key: GEODE-2122
>                 URL: https://issues.apache.org/jira/browse/GEODE-2122
>             Project: Geode
>          Issue Type: Bug
>          Components: wan
>            Reporter: nabarun
>
> Replication steps:
> 1. Create two WAN sites A and B
> 2. A contains two senders
> 3. B contains one receiver and another member but do not create a receiver on it.
> 4. On the single receiver, using {code}WANTestBase.cache.getResourceManager().setCriticalHeapPercentage(0.05f); {code}make sure that it is low on memory when it has used up 5% of the memory.
> 5. Do some puts on the senders.
> 6. We see that low on memory exception is sent to the sender but the sender still keeps on sending and the receiver still accepts the puts.
> Case 2:
> 1. Same steps as above but execute {code}WANTestBase.cache.getResourceManager().setCriticalHeapPercentage(0.05f); {code}on the the member on WAN site B which is not the receiver.
> 2. In this case when we do the puts, and the memory threshold is reached in the member, the puts are being rejected.
> We need the behavior to be same in both the cases i.e. puts should be rejected when anybody is low on memory.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)