[jira] [Comment Edited] (FLINK-23705) Unregister MetricGroup after shard closes in Kinesis connector

["Danny Cranmer (Jira)" <ji...@apache.org>]

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

Danny Cranmer edited comment on FLINK-23705 at 8/11/21, 7:48 AM:
-----------------------------------------------------------------

Thanks [~elphastori]. The fix for this will be ported from [here|https://github.com/awslabs/amazon-kinesis-connector-flink/pull/43]


was (Author: dannycranmer):
Thanks [~elphastori]. This issue will be ported from [here|https://github.com/awslabs/amazon-kinesis-connector-flink/pull/43]

> Unregister MetricGroup after shard closes in Kinesis connector
> --------------------------------------------------------------
>
>                 Key: FLINK-23705
>                 URL: https://issues.apache.org/jira/browse/FLINK-23705
>             Project: Flink
>          Issue Type: Bug
>          Components: Connectors / Kinesis
>    Affects Versions: 1.6.3, 1.6.4, 1.7.2, 1.8.0, 1.8.1, 1.8.2, 1.8.3, 1.9.0, 1.9.1, 1.9.2, 1.9.3, 1.10.0, 1.10.1, 1.10.2, 1.10.3, 1.11.0, 1.11.1, 1.11.2, 1.11.3, 1.11.4, 1.12.0, 1.12.1, 1.12.2, 1.13.0, 1.12.3, 1.13.1, 1.12.4, 1.12.5, 1.13.2
>            Reporter: Elphas Toringepi
>            Priority: Minor
>             Fix For: 1.14.0, 1.13.3
>
>
> Kinesis connector continues to report metrics for closed shards after resharding leading to incorrect millisBehindLatest metric reported on the Flink dashboard.
> This is results in incorrect aggregated metrics for the entire stream even after restarting.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)