[
https://issues.apache.org/jira/browse/KAFKA-4094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17852661#comment-17852661
]
Ksolves commented on KAFKA-4094:
--------------------------------
Hi [~jkreps]
Can you please confirm where the change needs to be implemented? Also, which
component or file does it belong to? Seems like we only need to make changes to
the broker config. Please confirm
Lastly, from my understanding, broker configurations should be categorized by
their priority as below:
*HIGH Priority:*
* broker.id
* listerners
*MEDIUM Priority:*
* log.dirs
* num.partitions
* log.cleanup.policy
*LOW Priority:*
* message.max.bytes
* replica.fetch.max.bytes
* log.segment.bytes
Please confirm if this is correct or if there are any additional configurations
or details to consider.
> Fix importance labels for Kafka Server config
> ---------------------------------------------
>
> Key: KAFKA-4094
> URL: https://issues.apache.org/jira/browse/KAFKA-4094
> Project: Kafka
> Issue Type: Bug
> Reporter: Jay Kreps
> Priority: Major
> Labels: newbie
>
> We have > 100 server configs. The importance label is meant to help people
> navigate this in a sane way. The intention is something like the following:
> HIGH - things you must think about and set
> MEDIUM - things you don't necessarily need to set but that you might want to
> tune
> LOW - thing you probably don't need to set
> Currently we have a gazillion things marked as high including very subtle
> tuning params and also things marked as deprecated (which probably should be
> its own importance level). This makes it really hard for people to figure out
> which configurations to actually learn about and use.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
