You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@kafka.apache.org by "Jun Rao (JIRA)" <ji...@apache.org> on 2018/10/09 17:47:00 UTC

[jira] [Resolved] (KAFKA-7366) topic level segment.bytes and segment.ms not taking effect immediately

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

Jun Rao resolved KAFKA-7366.
----------------------------
       Resolution: Fixed
    Fix Version/s: 2.1.0

Merged to 2.1 and trunk.

> topic level segment.bytes and segment.ms not taking effect immediately
> ----------------------------------------------------------------------
>
>                 Key: KAFKA-7366
>                 URL: https://issues.apache.org/jira/browse/KAFKA-7366
>             Project: Kafka
>          Issue Type: Bug
>    Affects Versions: 1.1.0, 2.0.0
>            Reporter: Jun Rao
>            Assignee: Manikumar
>            Priority: Major
>             Fix For: 2.1.0
>
>
> It used to be that topic level configs such as segment.bytes takes effect immediately. Because of KAFKA-6324 in 1.1, those configs now only take effect after the active segment has rolled. The relevant part of KAFKA-6324 is that in Log.maybeRoll, the checking of the segment rolling is moved to LogSegment.shouldRoll().



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)