You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Bruce Schuchardt (JIRA)" <ji...@apache.org> on 2018/02/07 22:27:00 UTC
[jira] [Updated] (GEODE-4627) Protobuf server operation handlers do
not check for low-memory conditions
[ https://issues.apache.org/jira/browse/GEODE-4627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bruce Schuchardt updated GEODE-4627:
------------------------------------
Issue Type: Bug (was: Task)
> Protobuf server operation handlers do not check for low-memory conditions
> -------------------------------------------------------------------------
>
> Key: GEODE-4627
> URL: https://issues.apache.org/jira/browse/GEODE-4627
> Project: Geode
> Issue Type: Bug
> Components: client/server
> Reporter: Bruce Schuchardt
> Priority: Major
>
> The new Protobuf-based client/server operation handlers are not checking to see if memory is low. For instance, the Java client does this check in handling function execution requests:
> {code}
> HeapMemoryMonitor hmm =
> ((InternalResourceManager) cache.getResourceManager()).getHeapMonitor();
> if (functionObject.optimizeForWrite() && cache != null && hmm.getState().isCritical()
> && !MemoryThresholds.isLowMemoryExceptionDisabled()) {
> Set<DistributedMember> sm = Collections.singleton((DistributedMember) cache.getMyId());
> Exception e = new LowMemoryException(
> LocalizedStrings.ResourceManager_LOW_MEMORY_FOR_0_FUNCEXEC_MEMBERS_1
> .toLocalizedString(new Object[] {functionObject.getId(), sm}),
> sm);
> sendException(hasResult, clientMessage, e.getMessage(), serverConnection, e);
> return;
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)