[
https://issues.apache.org/jira/browse/FLINK-6280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15975046#comment-15975046
]
ASF GitHub Bot commented on FLINK-6280:
---------------------------------------
Github user greghogan commented on the issue:
https://github.com/apache/flink/pull/3701
I had provided some examples in the JIRA, but yes, it allows delaying
evaluation of the java opts (with double quotes) until immediately before the
daemon is started. This allows creating additional log files such as for JFR or
JitWatch (the two use cases I have needed, I expect there are more). In
addition the log rotation, Flink may be running multiple TaskManagers on the
same instance so reusing Flink's log naming scheme prevents overwriting files.
> Allow logging with Java flags
> -----------------------------
>
> Key: FLINK-6280
> URL: https://issues.apache.org/jira/browse/FLINK-6280
> Project: Flink
> Issue Type: Improvement
> Components: Startup Shell Scripts
> Affects Versions: 1.3.0
> Reporter: Greg Hogan
> Assignee: Greg Hogan
>
> Allow configuring Flink's Java options with the logging prefix and log
> rotation. For example, this allows the following configurations to write
> {{.jfr}} and {{.jit}} files alongside the existing {{.log}} and {{.out}}
> files.
> {code:language=bash|title=Configuration for Java Flight Recorder}
> env.java.opts: "-XX:+UnlockCommercialFeatures -XX:+UnlockDiagnosticVMOptions
> -XX:+FlightRecorder -XX:+DebugNonSafepoints
> -XX:FlightRecorderOptions=defaultrecording=true,dumponexit=true,dumponexitpath=${LOG_PREFIX}.jfr"
> {code}
> {code:language=bash|title=Configuration for JitWatch}
> env.java.opts: "-XX:+UnlockDiagnosticVMOptions -XX:+TraceClassLoading
> -XX:+LogCompilation -XX:LogFile=${LOG_PREFIX}.jit -XX:+PrintAssembly"
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
