[
https://issues.apache.org/jira/browse/FLINK-3678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15219122#comment-15219122
]
ASF GitHub Bot commented on FLINK-3678:
---------------------------------------
Github user stefanobaghino commented on a diff in the pull request:
https://github.com/apache/flink/pull/1837#discussion_r57986135
--- Diff: docs/setup/config.md ---
@@ -275,6 +275,10 @@ For example when running Flink on YARN on an
environment with a restrictive fire
- `recovery.job.delay`: (Default 'akka.ask.timeout') Defines the delay
before persisted jobs are recovered in case of a recovery situation.
+## Environment
+
+- `env.log.dir`: (Defaults to the `log` directory under Flink's home)
Defines the directory where the Flink logs are saved.
--- End diff --
I did some research but checking for a valid path across all possible
operative systems and filesystems would be prohibitive, I guess we'll have to
settle for the documentation at this time. :smiley: Thanks for pointing it out!
> Make Flink logs directory configurable
> --------------------------------------
>
> Key: FLINK-3678
> URL: https://issues.apache.org/jira/browse/FLINK-3678
> Project: Flink
> Issue Type: Improvement
> Components: Start-Stop Scripts
> Affects Versions: 1.0.0
> Reporter: Stefano Baghino
> Assignee: Stefano Baghino
> Priority: Minor
> Fix For: 1.0.1
>
>
> Currently Flink logs are stored under {{$FLINK_HOME/log}} and the user cannot
> configure an alternative storage location. It would be nice to add a
> configuration key in the {{flink-conf.yaml}} and edit the {{bin/flink}}
> launch script accordingly to get the value if present or default to the
> current behavior if no value is provided.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
