You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Jason Gustafson (JIRA)" <ji...@apache.org> on 2016/10/04 03:24:20 UTC

[jira] [Updated] (KAFKA-4019) LogCleaner should grow read/write buffer to max message size for the topic

     [ https://issues.apache.org/jira/browse/KAFKA-4019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason Gustafson updated KAFKA-4019:
-----------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

Issue resolved by pull request 1758
[https://github.com/apache/kafka/pull/1758]

> 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
>            Priority: Critical
>             Fix For: 0.10.1.0
>
>
> 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)