[
https://issues.apache.org/jira/browse/FLINK-15792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17110083#comment-17110083
]
Yang Wang commented on FLINK-15792:
-----------------------------------
[~trohrmann] No, even after FLINK-17166, we still could not achieve this for
native k8s. Because we are using {{log4j.properties}} for the JobManager and
TaskManager start command.
Of cause, we could simply change it to {{flink-console.properties}}. And then
the STDOUT/STDERR could not be accessed via web dashboard. I think this is a
burden.
For the solution in current doc[1], the STDOUT/STDERR could be accessed via
dashboard, but not {{kubectl logs}}.
[1].
[https://ci.apache.org/projects/flink/flink-docs-master/ops/deployment/native_kubernetes.html#log-files]
> Make Flink logs accessible via kubectl logs per default
> -------------------------------------------------------
>
> Key: FLINK-15792
> URL: https://issues.apache.org/jira/browse/FLINK-15792
> Project: Flink
> Issue Type: Sub-task
> Components: Deployment / Kubernetes
> Affects Versions: 1.10.0
> Reporter: Till Rohrmann
> Priority: Major
> Fix For: 1.11.0, 1.10.2
>
>
> I think we should make Flink's logs accessible via {{kubectl logs}} per
> default. Firstly, this is the idiomatic way to obtain the logs from a
> container on Kubernetes. Secondly, especially if something does not work and
> the container cannot start/stops abruptly, there is no way to log into the
> container and look for the log.file. This makes debugging the setup quite
> hard.
> I think the best way would be to create the Flink Docker image in such a way
> that it logs to stdout. In order to allow access to the log file from the web
> ui, it should also create a log file. One way to achieve this is to add a
> ConsoleAppender to the respective logging configuration. Another way could be
> to start the process in the console mode and then to teeing the stdout output
> into the log file.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
