geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GEODE-3198) Do not prevent bucket creation if local-max-memory is exceeded
Date Fri, 14 Jul 2017 18:57:00 GMT

    [ https://issues.apache.org/jira/browse/GEODE-3198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16087797#comment-16087797
] 

ASF GitHub Bot commented on GEODE-3198:
---------------------------------------

Github user asfgit closed the pull request at:

    https://github.com/apache/geode/pull/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)

Mime
View raw message