[
https://issues.apache.org/jira/browse/FLINK-15489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17011627#comment-17011627
]
Yadong Xie commented on FLINK-15489:
------------------------------------
[~gjy]
I think the HTTP_CACHE_SECONDS is a trade-off, decrease the cache time could
help users to get more real-time logs, but it would also increase the pressure
of the rest API.
The HTTP_CACHE_SECONDS was set to 300 seconds since 5 years ago
[https://github.com/apache/flink/blame/6f2e9abffb0b1ef68e4f2cf058a24524b61e88a1/flink-runtime/src/main/java/org/apache/flink/runtime/rest/handler/legacy/files/StaticFileServerHandler.java#L104]
> Cannot update jobmanager/taskmanager logs
> -----------------------------------------
>
> Key: FLINK-15489
> URL: https://issues.apache.org/jira/browse/FLINK-15489
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Web Frontend
> Affects Versions: 1.9.1, 1.10.0
> Reporter: Dawid Wysakowicz
> Priority: Blocker
> Fix For: 1.10.0
>
> Attachments: screenshot-1.png
>
>
> There is no way to query the latest state of logs of jobmanager/taskmanager.
> The Web UI show only the first version that was ever displayed.
> How to reproduce:
> * (not sure if necessary) configure logback as described here:
> https://ci.apache.org/projects/flink/flink-docs-stable/dev/best_practices.html#use-logback-when-running-flink-on-a-cluster
> * start a cluster
> * show jobmanager logs in the Web UI
> * run example job
> * check again the jobmanager logs, there is no trace of the job. Clicking the
> refresh button does not help
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
