[
https://issues.apache.org/jira/browse/FLINK-6477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16004187#comment-16004187
]
Chesnay Schepler commented on FLINK-6477:
-----------------------------------------
Well my explanation covers why this can work if one is lucky. The first call to
load metrics starts a new metrics update, and gets nothing as a result. The
second call to load metrics may actually get results if the fetching of the
metrics finished between these 2 calls. But there's no guarantee that the
fetching finishes in time, so this would introduce a race condition.
> The first time to click Taskmanager cannot get the actual data
> --------------------------------------------------------------
>
> Key: FLINK-6477
> URL: https://issues.apache.org/jira/browse/FLINK-6477
> Project: Flink
> Issue Type: Bug
> Components: Webfrontend
> Affects Versions: 1.2.0
> Reporter: zhihao chen
> Assignee: zhihao chen
> Attachments: errDisplay.jpg
>
>
> Flink web page first click Taskmanager to get less than the actual data, when
> the parameter “jobmanager.web.refresh-interval” is set to a larger value, eg:
> 1800000, if you do not manually refresh the page you need to wait time after
> the timeout normal display
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
