[
https://issues.apache.org/jira/browse/GEODE-10117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17504611#comment-17504611
]
ASF subversion and git services commented on GEODE-10117:
---------------------------------------------------------
Commit ac0c3d53f0bdbbe3105a00b40c077b3c2a6c26fd in geode's branch
refs/heads/develop from Nabarun Nag
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=ac0c3d5 ]
GEODE-10117: Added section in docs about memory (#7439)
* Added section in the doc about lru max memory being over written if
local max memory is set.
* Also mentioned that these two settings are local and not cluster wide
* Format change to preserve existing note alongside the new one.
Co-authored-by: Dave Barnes <dav...@vmware.com>
> 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
>
> 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)
