[
https://issues.apache.org/jira/browse/FLINK-10243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16606654#comment-16606654
]
ASF GitHub Bot commented on FLINK-10243:
----------------------------------------
Clarkkkkk commented on issue #6658: [FLINK-10243][metrics] Make latency metrics
granularity configurable
URL: https://github.com/apache/flink/pull/6658#issuecomment-419305397
LGTM. Just one more proposal, could you add a global latency granularity to
to the metrics, that could be a great help.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> Add option to reduce latency metrics granularity
> ------------------------------------------------
>
> Key: FLINK-10243
> URL: https://issues.apache.org/jira/browse/FLINK-10243
> Project: Flink
> Issue Type: Sub-task
> Components: Configuration, Metrics
> Affects Versions: 1.7.0
> Reporter: Chesnay Schepler
> Assignee: Chesnay Schepler
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.7.0
>
>
> The latency is currently tracked separately from each operator subtask to
> each source subtask. The total number of latency metrics in the cluster is
> thus {{(# of sources) * (# of operators) * parallelism²}}, i.e. quadratic
> scaling.
> If we'd ignore the source subtask the scaling would be a lot more manageable.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
