[
https://issues.apache.org/jira/browse/FLINK-6477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16004376#comment-16004376
]
Chesnay Schepler commented on FLINK-6477:
-----------------------------------------
Again, that doesn't guarantee anything, for the same reasons i explained above.
Your test is flawed; it doesn't take latency into account, or the dropping of
messages, or the TM taking too long to respond.
The only ways i see to fix this is to either not return the current state but
block until the update is finished (which would make the WebUI probably
unresponsive) or to respond with the update state asynchronously (where I don't
know whether it is possible).
> 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)
