[
https://issues.apache.org/jira/browse/FLINK-31233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17730399#comment-17730399
]
Weihua Hu commented on FLINK-31233:
-----------------------------------
After offline discussion with [~guoyangze],
1. This change should only apply to TaskManagerStdoutFileHandler and should not
affect processing of other files.
2. Users need to be informed on the web UI that the stdout file does not exist,
probably because in K8S mode, they can use 'kubectl logs' to get the stdout
context.
> no error should be logged when retrieving the task manager's stdout if it
> does not exist
> -----------------------------------------------------------------------------------------
>
> Key: FLINK-31233
> URL: https://issues.apache.org/jira/browse/FLINK-31233
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / REST
> Affects Versions: 1.17.0
> Reporter: Weihua Hu
> Priority: Minor
> Labels: pull-request-available
> Fix For: 1.18.0
>
> Attachments: image-2023-02-27-13-56-40-718.png,
> image-2023-02-27-13-57-27-190.png
>
>
> When running Flink on Kubernetes, the stdout logs is not redirected to files
> so it will not shown in WEB UI. This is as expected.
> But It returns “500 Internal error” in REST API and produces an error log in
> jobmanager.log. This is confusing and misleading.
>
> I think this API should return “404 Not Found” without any error logs,
> similar to how jobmanager/stdout works.
>
> !image-2023-02-27-13-57-27-190.png!
> !image-2023-02-27-13-56-40-718.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
