You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Chesnay Schepler (JIRA)" <ji...@apache.org> on 2018/08/07 14:03:00 UTC
[jira] [Commented] (FLINK-10096) Metrics report incorrect subtask
ids
[ https://issues.apache.org/jira/browse/FLINK-10096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16571703#comment-16571703 ]
Chesnay Schepler commented on FLINK-10096:
------------------------------------------
Classic indexing conundrum.
The metric system uses the subtask index as returned by virtually all methods in the runtime, which is 0-indexed. The stringified name is 1-indexed.
> Metrics report incorrect subtask ids
> ------------------------------------
>
> Key: FLINK-10096
> URL: https://issues.apache.org/jira/browse/FLINK-10096
> Project: Flink
> Issue Type: Bug
> Components: Metrics
> Affects Versions: 1.6.0
> Reporter: Piotr Nowojski
> Priority: Major
>
> Subtask id is of by one when it's being reported by metrics compared to what is printed by {{StreamTask.toString()}}. For example metrics line:
> Initial sorter.137.buffers.inputQueueLength: 392
> vs actual name of this subtask:
> Initial sorter (138/192)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)