You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2021/02/18 15:00:00 UTC
[jira] [Commented] (NIFI-8231) Clarify documentation for
MonitorMemory Memory Pool allowable values
[ https://issues.apache.org/jira/browse/NIFI-8231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17286516#comment-17286516 ]
ASF subversion and git services commented on NIFI-8231:
-------------------------------------------------------
Commit 042b34cb435c6a54ed94b8149e1d4b4dfbec4ce1 in nifi's branch refs/heads/main from Joey Frazee
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=042b34c ]
NIFI-8231 Clarify behavior of allowed values for Memory Pools in MonitorMemory
> Clarify documentation for MonitorMemory Memory Pool allowable values
> --------------------------------------------------------------------
>
> Key: NIFI-8231
> URL: https://issues.apache.org/jira/browse/NIFI-8231
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Documentation & Website
> Affects Versions: 1.14.0
> Reporter: Joey Frazee
> Priority: Minor
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The allowable values for the Memory Pools isn't static but varies by platform and JVM. The docs don't indicate that so there are a few things that need to be clarified in the processor documentation since the published docs may vary:
> * The allowable values for Memory Pools is just an example.
> * Moving a flow between different JVMs or platforms might invalidate the reporting service if you configure a memory pool that exists on one and not the other.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)