You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Tadhg Pearson (JIRA)" <ji...@apache.org> on 2017/11/14 17:02:00 UTC

[jira] [Created] (KAFKA-6207) Include start of record when RecordIsTooLarge

Tadhg Pearson created KAFKA-6207:
------------------------------------

             Summary: Include start of record when RecordIsTooLarge
                 Key: KAFKA-6207
                 URL: https://issues.apache.org/jira/browse/KAFKA-6207
             Project: Kafka
          Issue Type: Bug
          Components: producer 
    Affects Versions: 0.10.1.1
            Reporter: Tadhg Pearson
            Priority: Minor


When a message is too large to be send (at org.apache.kafka.clients.producer.KafkaProducer#doSend), the RecordTooLargeException should carry the start of the record (for example, the first 1KB) so that the calling application can debug which message caused the error. 

For example: one common use case of Kafka is logging. The RecordTooLargeException is thrown due to a large log message being sent by the application. How do you know which statement in your application logged this large message? If your exception has thousands of logging statements, it will be very tough to find which one is the cause today.... but you include the start of the message, this could prove a very strong hint as to the cause!





--
This message was sent by Atlassian JIRA
(v6.4.14#64029)