flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Piotr Nowojski (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-10096) Metrics report incorrect subtask ids
Date Thu, 25 Oct 2018 13:39:00 GMT

    [ https://issues.apache.org/jira/browse/FLINK-10096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16663743#comment-16663743
] 

Piotr Nowojski commented on FLINK-10096:
----------------------------------------

[~Zentol] while I get that this Issue doesn't have the highest priority, but saying that we
"won't fix it" is a bit sad. I personally wasted some time trying to figure out what's going
on before I figured out this mismatch. We still should fix it at some point.

> 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)

Mime
View raw message