[
https://issues.apache.org/jira/browse/FLINK-33221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhanghao Chen updated FLINK-33221:
----------------------------------
Fix Version/s: 1.19.0
> Add config options for administrator JVM options
> ------------------------------------------------
>
> Key: FLINK-33221
> URL: https://issues.apache.org/jira/browse/FLINK-33221
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Configuration
> Reporter: Zhanghao Chen
> Assignee: Zhanghao Chen
> Priority: Major
> Fix For: 1.19.0
>
>
> We encounter similar issues described in SPARK-23472. Users may need to add
> JVM options to their Flink applications (e.g. to tune GC options). They
> typically use {{env.java.opts.x}} series of options to do so. We also have a
> set of administrator JVM options to apply by default, e.g. to enable GC log,
> tune GC options, etc. Both use cases will need to set the same series of
> options and will clobber one another.
> In the past, we generated and pretended to the administrator JVM options in
> the Java code for generating the starting command for JM/TM. However, this
> has been proven to be difficult to maintain.
> Therefore, I propose to also add a set of default JVM options for
> administrator use that prepends the user-set extra JVM options. We can mark
> the existing {{env.java.opts.x}} series as user-set extra JVM options and add
> a set of new {{env.java.opts.x.default}} options for administrator use.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
