geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nick Reich (JIRA)" <>
Subject [jira] [Assigned] (GEODE-3198) Do not prevent bucket creation if local-max-memory is exceeded
Date Wed, 12 Jul 2017 21:13:00 GMT


Nick Reich reassigned GEODE-3198:

    Assignee: Nick Reich

> Do not prevent bucket creation if local-max-memory is exceeded
> --------------------------------------------------------------
>                 Key: GEODE-3198
>                 URL:
>             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

View raw message