kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matthias J. Sax (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-5055) Kafka Streams skipped-records-rate sensor producing nonzero values even when FailOnInvalidTimestamp is used as extractor
Date Sun, 30 Apr 2017 05:07:04 GMT

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

Matthias J. Sax commented on KAFKA-5055:
----------------------------------------

[~dpoldrugo] Thanks a lot for looking into this. I agree that this is the bug we are looking
for (it was my guess anyway, that the reported value is just not correct.

Please go ahead with the PR.

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

Mime
View raw message