[
https://issues.apache.org/jira/browse/FLINK-31233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17703857#comment-17703857
]
Weihua Hu commented on FLINK-31233:
-----------------------------------
[~Weijie Guo] Thanks for your attention.
Yes, the stdout file not exists is the expected behavior. So we should return
the "404 Not found" response and not print log in jobmanager/taskmanager(or
maybe print debug level), just like
AbstractJobManagerFileHandler#respondToRequest did
> 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)
