Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
1.7.0
-
None
-
None
Description
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/...
Attachments
Issue Links
- links to