THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
Status
Current state: "Under Discussion"
Discussion thread: here
JIRA: KAFKA-13040 KAFKA-7760
Please keep the discussion on the mailing list rather than commenting on the wiki (wiki discussions get unwieldy fast).
Motivation
Many times, Kafka brokers in production crash with "Too many open files" error or "Out of memory" errors because some Kafka topics have a lot of segment files as a result of small segment.ms or segment.bytes. These two configuration can be set by any user who is authorized to create topic or modify topic configuration.
To prevent these two configuration from causing Kafka broker crash, they should have a minimum value that is big enough.
Public Interfaces
This KIP proposes to add these two broker configuration:
min.topic.segment.msmin.topic.segment.bytes
This KIP proposes changes to the validation of the following topic configuration:
segment.mssegment.bytes
Proposed Changes
This KIP proposes to add the following dynamic broker configuration:
| Configuration | Type | Default value | Documentation |
|---|---|---|---|
| min.topic.segment.ms | long | 3600000 | The minimum value for topic configuration segment.ms. |
| min.topic.segment.bytes | int | 1048576 | The minimum value for topic configuration segment.bytes. |
When provided via CreateTopics or AlterConfigs API, the validation of the following topic configuration changes as follow:
| Topic configuration | Validation |
|---|---|
segment.ms | If the value of segment.ms is less than the value of min.topic.segment.ms, Kafka broker will reject it by responding with InvalidConfigurationException |
segment.bytes | If the value of segment.bytes is less than the value of min.topic.segment.bytes, Kafka broker will reject it by responding with InvalidConfigurationException |
Compatibility, Deprecation, and Migration Plan
Kafka brokers that have existing topics with segment.ms less than min.topic.segment.ms and/or segment.bytes less than min.topic.segment.bytes would have a warning message in the log.
Rejected Alternatives
- Set a fixed minimum value for segment.ms and segment.bytes. The reason this approach is rejected is because there are use cases that requires setting segment.ms or segment bytes to very small value. For example: deleting all records in a topic by setting segment.bytes to 0 temporarily.