You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Guozhang Wang (JIRA)" <ji...@apache.org> on 2017/05/02 01:59:04 UTC
[jira] [Commented] (KAFKA-5055) Kafka Streams skipped-records-rate
sensor producing nonzero values even when FailOnInvalidTimestamp is used as
extractor
[ https://issues.apache.org/jira/browse/KAFKA-5055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15991978#comment-15991978 ]
Guozhang Wang commented on KAFKA-5055:
--------------------------------------
[~dpoldrugo] Thanks! Added.
> Kafka Streams skipped-records-rate sensor producing nonzero values even when FailOnInvalidTimestamp is used as extractor
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: KAFKA-5055
> URL: https://issues.apache.org/jira/browse/KAFKA-5055
> Project: Kafka
> Issue Type: Bug
> Components: streams
> Reporter: Nikki Thean
> Assignee: Guozhang Wang
>
> According to the code and the documentation for this metric, the only reason for a skipped record is an invalid timestamp, except that a) I am reading from a topic that is populated solely by Kafka Connect and b) I am using `FailOnInvalidTimestamp` as the timestamp extractor.
> Either I'm missing something in the documentation (i.e. another reason for skipped records) or there is a bug in the code that calculates this metric.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)