[
https://issues.apache.org/jira/browse/FLINK-8410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17321607#comment-17321607
]
Flink Jira Bot commented on FLINK-8410:
---------------------------------------
This issue and all of its Sub-Tasks have not been updated for 180 days. So, it
has been labeled "stale-minor". If you are still affected by this bug or are
still interested in this issue, please give an update and remove the label. In
7 days the issue will be closed automatically.
> Kafka consumer's commitedOffsets gauge metric is prematurely set
> ----------------------------------------------------------------
>
> Key: FLINK-8410
> URL: https://issues.apache.org/jira/browse/FLINK-8410
> Project: Flink
> Issue Type: Bug
> Components: Connectors / Kafka, Runtime / Metrics
> Affects Versions: 1.3.2, 1.4.0, 1.5.0
> Reporter: Tzu-Li (Gordon) Tai
> Priority: Minor
> Labels: stale-minor
>
> The {{committedOffset}} metric gauge value is set too early. It is set here:
> https://github.com/apache/flink/blob/master/flink-connectors/flink-connector-kafka-0.10/src/main/java/org/apache/flink/streaming/connectors/kafka/internal/Kafka010Fetcher.java#L224
> This sets the committed offset before the actual commit happens, which varies
> depending on whether the commit mode is auto periodically, or committed on
> checkpoints. Moreover, in the 0.9+ consumers, the {{KafkaConsumerThread}} may
> choose to supersede some commit attempts if the commit takes longer than the
> commit interval.
> While the committed offset back to Kafka is not a critical value used by the
> consumer, it will be best to have more accurate values as a Flink-shipped
> metric.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
