You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/03/07 08:24:33 UTC
[jira] [Commented] (FLUME-3067) Defalut JAVA_OPTS "-Xmx20m" may
be conflicted with cuctom defines.
[ https://issues.apache.org/jira/browse/FLUME-3067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15898942#comment-15898942 ]
ASF GitHub Bot commented on FLUME-3067:
---------------------------------------
GitHub user chenjianwei3 opened a pull request:
https://github.com/apache/flume/pull/112
"[FLUME-3067][Shell]Defalut JAVA_OPTS "-Xmx20m" may be conflicted with cuctom defines."
When write a Flume bootstrap shell, set the environment variable FLUME_JAVA_OPTS with the defined values as the min(-Xms)
and max(-Xmx) heap size for the JVM, then call "bin/flime-ng" to start Flume.
Succeed to start, but the defalut "-Xmx20m" is still in process JVM options.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/chenjianwei3/flume chenjianwei3branch
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flume/pull/112.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #112
----
commit 22ae3182fd4131ee1514f367879eb309d96172b6
Author: chenjianwei3 <ch...@zte.com.cn>
Date: 2017-03-07T08:19:13Z
"[FLUME-3067][Shell]Defalut JAVA_OPTS "-Xmx20m" may be conflicted with cuctom defines."
----
> Defalut JAVA_OPTS "-Xmx20m" may be conflicted with cuctom defines.
> --------------------------------------------------------------------
>
> Key: FLUME-3067
> URL: https://issues.apache.org/jira/browse/FLUME-3067
> Project: Flume
> Issue Type: Bug
> Components: Shell
> Affects Versions: v1.7.0
> Reporter: chenjianwei
>
> When write a Flume bootstrap shell, set the environment variable FLUME_JAVA_OPTS with the defined values as the min(-Xms)
> and max(-Xmx) heap size for the JVM, then call "bin/flime-ng" to start Flume. Succeed to start, but the defalut "-Xmx20m" is still in process JVM options.
> code
> :...
> export FLUME_JAVA_OPTS="-Xms100m -Xmx1024M -Dcom.sun.management.jmxremote"
> bin/flume-ng agent -c "$CONF_DIR" -f "$CONF_DIR"/flume-conf.properties -n "$agentname" -Dflume.monitoring.type=http -Dflume.monitoring.port="$port" & echo $! > "$PID_FILE"
> start Flume log:
> exec /usr/java/jdk/bin/java -Xmx20m -Xms100m -Xmx1024M -Dcom.sun.management.jmxremote -Dflume.monitoring.type=http -Dflume.monitoring.port=57080 -cp...
> process information:
> [root@zdh242 ~]# ps -ef |grep flume
> root 10399 1 10 09:53 pts/1 00:00:01 /usr/java/jdk/bin/java -Xmx20m -Xms100m -Xmx1024M -Dcom.sun.management.jmxremote -Dflume.monitoring.type=http -Dflu.port=57080 -cp /home/logSearch/conf:/home/logSearch/lib/*:/etc/yarn/conf:/opt/ZDH/parcels/lib/hadoop/lib/...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)