You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Robert Metzger (Jira)" <ji...@apache.org> on 2020/08/07 11:19:00 UTC

[jira] [Comment Edited] (FLINK-10140) Log files are not available via web UI in containerized environment

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

Robert Metzger edited comment on FLINK-10140 at 8/7/20, 11:18 AM:
------------------------------------------------------------------

This is not a problem anymore. I tested it with the native Kubernetes integration and I just started a Flink 1.11 JobManager, and the logs are accessible via the Web UI.

This issue has been resolved, I will close it.


was (Author: rmetzger):
This is not a problem anymore with the native Kubernetes integration.
I just started a Flink 1.11 JobManager, and the logs are accessible via the Web UI.

This issue has been resolved, I will close it.

> Log files are not available via web UI in containerized environment
> -------------------------------------------------------------------
>
>                 Key: FLINK-10140
>                 URL: https://issues.apache.org/jira/browse/FLINK-10140
>             Project: Flink
>          Issue Type: Bug
>          Components: Deployment / Docker, Deployment / Kubernetes
>    Affects Versions: 1.5.2, 1.6.0, 1.7.0
>            Reporter: Till Rohrmann
>            Priority: Major
>
> Since we start Flink components in the foreground (see {{flink-contrib/docker-flink/docker-entrypoint.sh}} and {{flink-container/docker/docker-entrypoint.sh}} we print the log statements to STDOUT and don't write them into a file. Consequently, the web UI cannot server the log files since they don't exist. 
> A simple way to fix the problem is to also create a log file like in daemon mode



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