You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Fred Krone (JIRA)" <ji...@apache.org> on 2017/06/15 20:37:00 UTC

[jira] [Updated] (GEODE-2719) The total-max-memory region attribute does not appear to do anything

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

Fred Krone updated GEODE-2719:
------------------------------
    Labels: storage_3  (was: )

> The total-max-memory region attribute does not appear to do anything
> --------------------------------------------------------------------
>
>                 Key: GEODE-2719
>                 URL: https://issues.apache.org/jira/browse/GEODE-2719
>             Project: Geode
>          Issue Type: Improvement
>          Components: docs, regions
>            Reporter: Darrel Schneider
>              Labels: storage_3
>
> I could not find that the "total-max-memory" region partitioned attribute does anything. If this is correct then it should be deprecated and removed in a future release. A user read the geode docs and expected it cause LRU eviction since this docs say this about it:
> {quote}
> Maximum combined megabytes of memory to be used by all processes hosting this region for all copies, primary and redundant.
> {quote}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)