flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-6280) Allow logging with Java flags
Date Wed, 19 Apr 2017 16:28:41 GMT

    [ https://issues.apache.org/jira/browse/FLINK-6280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15975013#comment-15975013

ASF GitHub Bot commented on FLINK-6280:

Github user StephanEwen commented on the issue:

    Can you explain a bit more what this change does exactly? Does it make sure that if you
put bash commands into the java opts to compute flags, it evaluates those?
    Can you elaborate why this needs a change in the log rotation logic?

> 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

View raw message