[
https://issues.apache.org/jira/browse/KAFKA-1026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14059050#comment-14059050
]
Guozhang Wang commented on KAFKA-1026:
--------------------------------------
There is a rare case when we can still hit the MessageSizeTooLargeException,
which is when compression is turned on, we can have overflow in the underlying
byte buffer due to inaccurate compression rate estimate and reallocate with
larger size. But this case would be very rare I think.
In general, I think most of the JIRAs related to the old producer can be closed
after 0.8.2 is released with the new producer officially replacing the old
producer.
> Dynamically Adjust Batch Size Upon Receiving MessageSizeTooLargeException
> -------------------------------------------------------------------------
>
> Key: KAFKA-1026
> URL: https://issues.apache.org/jira/browse/KAFKA-1026
> Project: Kafka
> Issue Type: Bug
> Reporter: Guozhang Wang
> Assignee: Guozhang Wang
> Labels: newbie++
> Fix For: 0.9.0
>
>
> Among the exceptions that can possibly received in Producer.send(),
> MessageSizeTooLargeException is currently not recoverable since the producer
> does not change the batch size but still retries on sending. It is better to
> have a dynamic batch size adjustment mechanism based on
> MessageSizeTooLargeException.
> This is related to KAFKA-998
--
This message was sent by Atlassian JIRA
(v6.2#6252)
