flink-issues mailing list archives

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

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

Chesnay Schepler commented on FLINK-10096:

I did not close it due to being low priority, but because I sincerely do not have any plans
to change the metric system as proposed here.

I'd rather change the string representation of stream-tasks since that is the inconsistent
part; it conflicts with the metric system, rest api and all(most?) logging messages that log
the subtask index .

> 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

View raw message