[
https://issues.apache.org/jira/browse/KAFKA-13017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom Bentley resolved KAFKA-13017.
---------------------------------
Fix Version/s: 3.1.0
Resolution: Fixed
> Excessive logging on sink task deserialization errors
> -----------------------------------------------------
>
> Key: KAFKA-13017
> URL: https://issues.apache.org/jira/browse/KAFKA-13017
> Project: Kafka
> Issue Type: Bug
> Components: KafkaConnect
> Affects Versions: 3.0.0, 2.7.0, 2.8.0
> Reporter: Chris Egerton
> Assignee: Chris Egerton
> Priority: Major
> Fix For: 3.1.0
>
>
> Even with {{errors.log.enable}} set to {{false}}, deserialization failures
> are still logged at {{ERROR}} level by the
> {{org.apache.kafka.connect.runtime.WorkerSinkTask}} namespace. This becomes
> problematic in pipelines with {{errors.tolerance}} set to {{all}}, and can
> generate excessive logging of stack traces when deserialization errors are
> encountered for most if not all of the records being consumed by a sink task.
> The logging added to the {{WorkerSinkTask}} class in KAFKA-9018 should be
> removed and, if necessary, any valuable information from it not already
> present in the log messages generated by Connect with {{errors.log.enable}}
> and {{errors.log.include.messages}} set to {{true}} should be added in that
> place instead.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
