[
https://issues.apache.org/jira/browse/NIFI-2860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15868717#comment-15868717
]
ASF GitHub Bot commented on NIFI-2860:
--------------------------------------
Github user markap14 commented on the issue:
https://github.com/apache/nifi/pull/1382
@pvillard31 I have no issues with the idea you're proposing here. I would
suggest, though, that we should use properties like
<nifi.jvm.heap.init>512m</nifi.jvm.heap.init> instead of
<nifi.jvm.heap.mb.init>512</nifi.jvm.heap.mb.init>. There's no need to enforce
that the units be in MB. Most often, if someone wants to change it, they'll
actually want to change to GB.
> Use different properties for JVM Heap Max and Min values
> --------------------------------------------------------
>
> Key: NIFI-2860
> URL: https://issues.apache.org/jira/browse/NIFI-2860
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Configuration
> Affects Versions: 0.6.1
> Reporter: Andrew Festa
> Assignee: Pierre Villard
>
> In the bootstrap.conf, the JVM memory settings are using maven filtering to
> set the default values. Currently the JVM memory settings (java.arg.2 and
> java.arg.3) are using the same property. These should be using different
> values so we can override them to different values.
> https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-resources/src/main/resources/conf/bootstrap.conf#L35-L36
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
