KAFKA-4094: Reclassify broker configs that have sensible defaults as MEDIUM importance#22019
Open
fru1tworld wants to merge 1 commit intoapache:trunkfrom
Open
KAFKA-4094: Reclassify broker configs that have sensible defaults as MEDIUM importance#22019fru1tworld wants to merge 1 commit intoapache:trunkfrom
fru1tworld wants to merge 1 commit intoapache:trunkfrom
Conversation
…MEDIUM importance
github-actions
bot
added
triage
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
https://issues.apache.org/jira/browse/KAFKA-4094
Too many broker configs are currently marked as HIGH importance,
making it difficult for users to identify the settings that truly
matter for their deployment. This reclassifies 22 server configs
from HIGH to MEDIUM — all have sensible defaults and rarely need
tuning in most environments.
Changed configs (4 files):
ServerConfigs: background.threads, num.replica.alter.log.dirs.threads, early.start.listenersSocketServerConfigs: socket.send.buffer.bytes, socket.receive.buffer.bytes, queued.max.requestsReplicationConfigs: replica.socket.timeout.ms, replica.socket.receive.buffer.bytes, replica.fetch.wait.max.ms, replica.fetch.min.bytes, num.replica.fetchers, replica.high.watermark.checkpoint.interval.ms, leader.imbalance.check.interval.secondsLogConfig: log.roll.jitter.ms/hours, log.delete.delay.ms, log.flush.offset.checkpoint.interval.ms, log.flush.start.offset.checkpoint.interval.ms, num.recovery.threads.per.data.dir, log.flush.interval.messages, log.flush.scheduler.interval.ms, log.flush.interval.msConfigs intentionally kept as HIGH: broker.id, listeners, log.retention., log.roll.time., min.insync.replicas, auto.create.topics.enable, delete.topic.enable, unclean.leader.election.enable, and others that are essential or affect data safety.