You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Dan Smith (JIRA)" <ji...@apache.org> on 2015/07/10 19:20:04 UTC

[jira] [Resolved] (GEODE-44) Rebalancing only considers leader region when deciding to enforce local-max-memory

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

Dan Smith resolved GEODE-44.
----------------------------
    Resolution: Fixed

This bug was resolved with the merge of feature/GEODE-8 into develop in b205339a0c567073906936afe08ae3003c341c0a 

[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=b205339 ]

> Rebalancing only considers leader region when deciding to enforce local-max-memory
> ----------------------------------------------------------------------------------
>
>                 Key: GEODE-44
>                 URL: https://issues.apache.org/jira/browse/GEODE-44
>             Project: Geode
>          Issue Type: Bug
>    Affects Versions: 1.0.0-incubating
>            Reporter: Dan Smith
>            Assignee: Dan Smith
>         Attachments: 0001-GEODE-44-Enforce-local-max-memory-per-region-when-re.patch
>
>
> Rebalancing/Redundancy will refuse to create or move a bucket to a node if that node will go over the configured local-max-memory setting, but only if eviction is not enabled for the region. This is because if eviction is enabled the region is not limited to the in memory size.
> However, PartitionRegionRebalanceOp.buildModel is only looking at the leader region in a set of colocated regions when deciding to enforce local-max-memory
> {code}
> boolean enforceLocalMaxMemory = !leaderRegion.isEntryEvictionPossible();
> {code}
> This means that if there is a parent region without eviction and colocated regions that do have eviction enabled, all those regions will enforce this constraint.
> The check on whether to enforce this constraint should be applied on a region-by-region basis. The PartitionRegionLoadModel is already tracking the size and local-max-memory for each colocated region, so it should be able to decide whether to check the constraint for each colocated region.



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