[
https://issues.apache.org/jira/browse/KAFKA-7366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16599003#comment-16599003
]
Jun Rao commented on KAFKA-7366:
--------------------------------
[~ijuma], it might be debatable. However, if all other topic level configs take
effect immediately, it seems that we should make that consistent for all
configs.
> 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
> Priority: Major
>
> 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)
