[
https://issues.apache.org/jira/browse/FLINK-7575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16155391#comment-16155391
]
ASF GitHub Bot commented on FLINK-7575:
---------------------------------------
Github user zentol commented on the issue:
https://github.com/apache/flink/pull/4647
@uce The checkstyle didn't catch it since the `runtime/executiongraph`
package isn't covered by checkstyle.
The flag will not fulfill the intended purpose after #4472 since the
fetched metrics will be inserted one by one and not atomically in batches
(neither as a whole nor by job/task/operator). The same issue applies to the
current master since `MutableIOMetric` doesn't synchronize on the metric store.
For the flag to properly work you will have to verify that every single
metric that you access from the store is not null. If any metric is null the
update isn't complete and you send back -1.
> Dashboard jobs/tasks metrics display 0 when metrics are not yet available
> -------------------------------------------------------------------------
>
> Key: FLINK-7575
> URL: https://issues.apache.org/jira/browse/FLINK-7575
> Project: Flink
> Issue Type: Improvement
> Components: Webfrontend
> Affects Versions: 1.3.2
> Reporter: James Lafa
> Assignee: James Lafa
> Priority: Minor
>
> The web frontend is currently displaying "0" when a metric is not available
> yet (ex: records-in/out, bytes-in/out).
> 0 is misleading and it's preferable to display no value while the value is
> still unknown.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
