[
https://issues.apache.org/jira/browse/FLINK-15489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17011699#comment-17011699
]
Yadong Xie commented on FLINK-15489:
------------------------------------
Hi [~dwysakowicz] [~gjy] [~trohrmann]
I just check the frontend again and can not reproduce the problem
1. when clicking the refresh button, you may need to wait some seconds before
the API response all data and refresh the frontend data, the log won't refresh
immediately.
!7A1CF604-032D-46D8-AC70-FBB884E868B9.png|width=536,height=349!
2. the request header from the frontend is no-cache(which means cache but
revalidate from sever)
[https://developer.mozilla.org/en-US/docs/Web/HTTP/Caching]
!6E9A4D72-6664-4B00-B02F-57EB2695D967.png|width=534,height=348!
> 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: 6E9A4D72-6664-4B00-B02F-57EB2695D967.png,
> 7A1CF604-032D-46D8-AC70-FBB884E868B9.png, 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)
