[ https://issues.apache.org/jira/browse/FLINK-15489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17011624#comment-17011624 ]
Gary Yao commented on FLINK-15489: ---------------------------------- An easy but maybe hacky fix would be to add a random query parameter to the GET request. > 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)