[
https://issues.apache.org/jira/browse/KAFKA-6834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17035922#comment-17035922
]
zhangzhisheng commented on KAFKA-6834:
--------------------------------------
kafka2.12_0.11.0.3 log clean tread stoped，throw exception info e.g
{code:java}
// code placeholder
java.lang.IllegalStateException: This log contains a message larger than
maximum allowable size of 1000000.
{code}
> log cleaner should handle the case when the size of a message set is larger
> than the max message size
> -----------------------------------------------------------------------------------------------------
>
> Key: KAFKA-6834
> URL: https://issues.apache.org/jira/browse/KAFKA-6834
> Project: Kafka
> Issue Type: Bug
> Reporter: Jun Rao
> Assignee: Rajini Sivaram
> Priority: Major
> Fix For: 2.0.0
>
>
> In KAFKA-5316, we added the logic to allow a message (set) larger than the
> per topic message size to be written to the log during log cleaning. However,
> the buffer size in the log cleaner is still bounded by the per topic message
> size. This can cause the log cleaner to die and cause the broker to run out
> of disk space.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
