You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2017/09/18 23:42:00 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16170904#comment-16170904 ]
ASF subversion and git services commented on GEODE-2719:
--------------------------------------------------------
Commit 280b5d7bf988a5170c458371097c9b07d295b6ae in geode's branch refs/heads/develop from [~abarve]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=280b5d7 ]
GEODE-2719: corrected GEODE versions to 1.3.0 instead of 1.2.2 for the
respective deprecated API javadocs.
> 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
> Assignee: Amey Barve
> 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)