[
https://issues.apache.org/jira/browse/FLINK-6477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16022403#comment-16022403
]
ASF GitHub Bot commented on FLINK-6477:
---------------------------------------
Github user zentol commented on the issue:
https://github.com/apache/flink/pull/3971
No it will happen very easily. Some TM does down, bam webUI is frozen for
10 seconds.
That's too much of an "if" for something that has a workaround; you can
refresh the page after all, or not effectively disable the web-refresh interval.
The update interval is set to 10 seconds by design to keep the additional
stress on the network as well as the JM/TM to a minimum. Especially in larger
deployments reducing the interval could have a noticeable effect; the current
policy however is that the metric system should not incur any noticeable
overhead.
> 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)
