[
https://issues.apache.org/jira/browse/KAFKA-7366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16635806#comment-16635806
]
ASF GitHub Bot commented on KAFKA-7366:
---------------------------------------
omkreddy opened a new pull request #5728: KAFKA-7366: Make topic configs
segment.bytes and segment.ms to take effect immediately
URL: https://github.com/apache/kafka/pull/5728
### Committer Checklist (excluded from commit message)
- [ ] Verify design and implementation
- [ ] Verify test coverage and CI build status
- [ ] Verify documentation (including upgrade notes)
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> 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
>
> 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)
