[jira] [Created] (FLINK-11169) [hotfix][runtime] fix the problem of not being reloaded for jobmanager's log after clicking the refresh button in web ui
Jiayong Mo created FLINK-11169: -- Summary: [hotfix][runtime] fix the problem of not being reloaded for jobmanager's log after clicking the refresh button in web ui Key: FLINK-11169 URL: https://issues.apache.org/jira/browse/FLINK-11169 Project: Flink Issue Type: Bug Components: REST Affects Versions: 1.7.0, 1.6.2 Reporter: Jiayong Mo In the Flink web UI page, we can access the log of jobmanager from the tab under its corresponding page, but we could not reload the log (the content is not up-to-date) since the log file has been cached for 300s in the local client' disk. And this problem occurs because of the incorrect way to check if the file should be cached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FLINK-11169) fix the problem of not being reloaded for jobmanager's log after clicking the refresh button in web ui
[ https://issues.apache.org/jira/browse/FLINK-11169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiayong Mo updated FLINK-11169: --- Summary: fix the problem of not being reloaded for jobmanager's log after clicking the refresh button in web ui (was: [hotfix][runtime] fix the problem of not being reloaded for jobmanager's log after clicking the refresh button in web ui) > fix the problem of not being reloaded for jobmanager's log after clicking the > refresh button in web ui > -- > > Key: FLINK-11169 > URL: https://issues.apache.org/jira/browse/FLINK-11169 > Project: Flink > Issue Type: Bug > Components: REST >Affects Versions: 1.6.2, 1.7.0 >Reporter: Jiayong Mo >Priority: Major > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > In the Flink web UI page, we can access the log of jobmanager from the tab > under its corresponding page, but we could not reload the log (the content is > not up-to-date) since the log file has been cached for 300s in the local > client' disk. And this problem occurs because of the incorrect way to check > if the file should be cached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
