[
https://issues.apache.org/jira/browse/KAFKA-7760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16860287#comment-16860287
]
ASF GitHub Bot commented on KAFKA-7760:
---------------------------------------
dulvinw commented on pull request #6911: KAFKA-7760
URL: https://github.com/apache/kafka/pull/6911
*Add broker configuration to set minimum value for segment.bytes and
segment.ms.*
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Add broker configuration to set minimum value for segment.bytes and segment.ms
> ------------------------------------------------------------------------------
>
> Key: KAFKA-7760
> URL: https://issues.apache.org/jira/browse/KAFKA-7760
> Project: Kafka
> Issue Type: Improvement
> Reporter: Badai Aqrandista
> Assignee: Dulvin Witharane
> Priority: Major
> Labels: kip, newbie
>
> If someone set segment.bytes or segment.ms at topic level to a very small
> value (e.g. segment.bytes=1000 or segment.ms=1000), Kafka will generate a
> very high number of segment files. This can bring down the whole broker due
> to hitting the maximum open file (for log) or maximum number of mmap-ed file
> (for index).
> To prevent that from happening, I would like to suggest adding two new items
> to the broker configuration:
> * min.topic.segment.bytes, defaults to 1048576: The minimum value for
> segment.bytes. When someone sets topic configuration segment.bytes to a value
> lower than this, Kafka throws an error INVALID VALUE.
> * min.topic.segment.ms, defaults to 3600000: The minimum value for
> segment.ms. When someone sets topic configuration segment.ms to a value lower
> than this, Kafka throws an error INVALID VALUE.
> Thanks
> Badai
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
