kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Liquan Pei (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (KAFKA-4136) KafkaBasedLog should include offsets it is trying to/successfully read to in log messages
Date Thu, 08 Sep 2016 16:44:21 GMT

     [ https://issues.apache.org/jira/browse/KAFKA-4136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Liquan Pei reassigned KAFKA-4136:
---------------------------------

    Assignee: Liquan Pei  (was: Ewen Cheslack-Postava)

> 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: Liquan Pei
>            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)

Mime
View raw message