[jira] [Updated] (FLINK-17677) FLINK_LOG_PREFIX recommended in docs is not always available

["Zhu Zhu (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/FLINK-17677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Zhu Zhu updated FLINK-17677:
----------------------------
    Fix Version/s:     (was: 1.9.4)
                       (was: 1.10.2)
                   1.10.3
                   1.11.2

> FLINK_LOG_PREFIX recommended in docs is not always available
> ------------------------------------------------------------
>
>                 Key: FLINK-17677
>                 URL: https://issues.apache.org/jira/browse/FLINK-17677
>             Project: Flink
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions: 1.9.3, 1.10.1, 1.11.0
>            Reporter: Xintong Song
>            Priority: Major
>             Fix For: 1.12.0, 1.11.2, 1.10.3
>
>
> The [Application Profiling & Debugging|https://ci.apache.org/projects/flink/flink-docs-master/monitoring/application_profiling.html] documentation recommend to use the script variable {{FLINK_LOG_PREFIX}} for defining log file paths. However, this variable is only available in standalone mode. This is a bit misleading for users of other deployments (see this [thread|http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Flink-Memory-analyze-on-AWS-EMR-td35036.html]).
> I propose to replace {{FLINK_LOG_PREFIX}} with a general representation {{<your-log-path>}}, and add a separate section to discuss how to set the log path (e.g., use {{FLINK_LOG_PREFIX}} with standalone deployments and {{<LOG_DIR>}} with Yarn deployments).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)