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 Nag (Jira)" <ji...@apache.org> on 2022/03/11 00:02:00 UTC

[jira] [Resolved] (GEODE-10117) Add doc section mentioning the relationship between local-max-memory and lru eviction memory

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

Nabarun Nag resolved GEODE-10117.
---------------------------------
    Fix Version/s: 1.16.0
       Resolution: Fixed

> Add doc section mentioning the relationship between local-max-memory and lru eviction memory
> --------------------------------------------------------------------------------------------
>
>                 Key: GEODE-10117
>                 URL: https://issues.apache.org/jira/browse/GEODE-10117
>             Project: Geode
>          Issue Type: Bug
>          Components: docs
>            Reporter: Nabarun Nag
>            Assignee: Nabarun Nag
>            Priority: Major
>              Labels: needsTriage, pull-request-available
>             Fix For: 1.16.0
>
>
> Section to be added :
> **Note:** For partition regions if the partition region attribute `local-max-memory` is set then the eviction attribute `lru-memory-size maximum` is overwritten with the value of `local-max-memory`
>         Both `local-max-memory` and `lru-memory-size maximum` are local member attributes and not cluster-wide. 



--
This message was sent by Atlassian Jira
(v8.20.1#820001)