[
https://issues.apache.org/jira/browse/KAFKA-4019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15426092#comment-15426092
]
ASF GitHub Bot commented on KAFKA-4019:
---------------------------------------
GitHub user rajinisivaram opened a pull request:
https://github.com/apache/kafka/pull/1758
KAFKA-4019: Update log cleaner to handle max message size of topics
Grow read and write buffers of cleaner up to the maximum message size of
the log being cleaned if the topic has larger max message size than the default
config of the broker.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/rajinisivaram/kafka KAFKA-4019
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/1758.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1758
----
commit fa89ba94cbc2abc54a94497c3207bb2bce62743a
Author: Rajini Sivaram <rajinisiva...@googlemail.com>
Date: 2016-08-18T08:08:17Z
KAFKA-4019: Update log cleaner to handle max message size of topics
----
> LogCleaner should grow read/write buffer to max message size for the topic
> --------------------------------------------------------------------------
>
> Key: KAFKA-4019
> URL: https://issues.apache.org/jira/browse/KAFKA-4019
> Project: Kafka
> Issue Type: Bug
> Components: core
> Affects Versions: 0.10.0.0
> Reporter: Jun Rao
> Assignee: Rajini Sivaram
>
> Currently, the LogCleaner.growBuffers() only grows the buffer up to the
> default max message size. However, since the max message size can be
> customized at the topic level, LogCleaner should allow the buffer to grow up
> to the max message allowed by the topic. Otherwise, the cleaner will get
> stuck on a large message.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
