[
https://issues.apache.org/jira/browse/GEODE-3198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16087796#comment-16087796
]
ASF subversion and git services commented on GEODE-3198:
--------------------------------------------------------
Commit 43d98e03f0cb1bdefcc7d18ba4a12272056475e7 in geode's branch
refs/heads/develop from [~nreich]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=43d98e0 ]
GEODE-3198: Allow bucket creation when over local-max-memory
The bucket will not be created on a member that is over local max
memory, unless all members have failed to create the bucket.
In that case the implementation sets a "force" flag that will
now cause the bucket to be created even on a member that is over
local max memory.
This closes #636
> Do not prevent bucket creation if local-max-memory is exceeded
> --------------------------------------------------------------
>
> Key: GEODE-3198
> URL: https://issues.apache.org/jira/browse/GEODE-3198
> Project: Geode
> Issue Type: Improvement
> Reporter: Nick Reich
> Assignee: Nick Reich
>
> In creating a new bucket, if local-max-memory is exceeded on all members, the
> bucket cannot be created until a member goes below that memory threshold
> (which may be never, in which case the attempt to create the bucket loops
> forever). Currently, if all members have indicated they should not make the
> bucket, the request is again made, but with a "force" flag set to true. This
> allows overriding the fact that the member believes it already hosts as many
> buckets as it should for balance, but does not override the local-max-memory
> check. We should therefore have the force flag also override the memory
> threshold check, thus allowing bucket creation to proceed, but still
> attempting to honor not adding it to a member already at or above its target
> memory limit.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
