You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Ewen Cheslack-Postava (JIRA)" <ji...@apache.org> on 2016/09/06 23:40:20 UTC

[jira] [Created] (KAFKA-4136) KafkaBasedLog should include offsets it is trying to/successfully read to in log messages

Ewen Cheslack-Postava created KAFKA-4136:
--------------------------------------------

             Summary: KafkaBasedLog should include offsets it is trying to/successfully read to in log messages
                 Key: KAFKA-4136
                 URL: https://issues.apache.org/jira/browse/KAFKA-4136
             Project: Kafka
          Issue Type: Bug
          Components: KafkaConnect
    Affects Versions: 0.10.0.1
            Reporter: Ewen Cheslack-Postava
            Assignee: Ewen Cheslack-Postava
            Priority: Minor


Including the offset information will aid in debugging. It'll need to be logged for all partitions, but often the # of partitions won't be too large and this helps to understand after an issue occurs what values were being used (e.g. for configs you can normally get this from DistributedHerder, but for the offsets topic, it allows you to dump the offsets topic and figure out what offset was being used even if the connector doesn't log any information itself).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)