You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Ryan Withers (Jira)" <ji...@apache.org> on 2019/09/30 18:42:00 UTC
[jira] [Resolved] (NIFI-6731) Docker container JVM heap not
applying
[ https://issues.apache.org/jira/browse/NIFI-6731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ryan Withers resolved NIFI-6731.
--------------------------------
Fix Version/s: 1.10.0
Resolution: Won't Fix
We found there was already an issue to deal with what we were seeing. We were looking at master thinking that the same thing was in the 1.9.x release we are working with. We have a solution for this while we wait for 1.10.0.
> Docker container JVM heap not applying
> --------------------------------------
>
> Key: NIFI-6731
> URL: https://issues.apache.org/jira/browse/NIFI-6731
> Project: Apache NiFi
> Issue Type: Bug
> Components: Docker
> Affects Versions: 1.9.2
> Reporter: cavemandaveman
> Priority: Major
> Fix For: 1.10.0
>
>
> The environment variables:
> *NIFI_JVM_HEAP_INIT*
> *NIFI_JVM_HEAP_MAX*
> do not get set properly once the container is running.
>
> For example, when setting these variables in the docker run command:
> *docker run -d -p 8080:8080 -e NIFI_JVM_HEAP_INIT=2g -e NIFI_JVM_HEAP_MAX=2g apache/nifi:1.9.2*
> then checking [http://localhost:8080/nifi-api/system-diagnostics] shows that *totalHeap* and *maxHeap* are set to the default 512mb. Also exec-ing into the container and looking at the bootstrap.conf shows that *java.arg.2* and *java.arg.3* did not get updated.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)