You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Weijie Guo (Jira)" <ji...@apache.org> on 2025/03/18 09:50:06 UTC

[jira] [Updated] (FLINK-37088) When the Flink application is running in k8s, the taskmanager log lacks a mount mapping to the host machine. Once the container is restarted, the log will disappear. It is necessary to have a log mount mapping to the host machine

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

Weijie Guo updated FLINK-37088:
-------------------------------
    Affects Version/s: 2.1.0
                           (was: 2.0.0)

> When the Flink application is running in k8s, the taskmanager log lacks a mount mapping to the host machine. Once the container is restarted, the log will disappear. It is necessary to have a log mount mapping to the host machine
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: FLINK-37088
>                 URL: https://issues.apache.org/jira/browse/FLINK-37088
>             Project: Flink
>          Issue Type: Improvement
>          Components: Deployment / Kubernetes
>    Affects Versions: 2.1.0
>            Reporter: baimafeimayf
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 2.0.0
>
>
> When the Flink application is running in k8s, the taskmanager log lacks a mount mapping to the host machine. Once the container is restarted, the log will disappear. It is necessary to have a log mount mapping to the host machine



--
This message was sent by Atlassian Jira
(v8.20.10#820010)