You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "Abhi (Jira)" <ji...@apache.org> on 2024/06/04 05:23:00 UTC

[jira] (KAFKA-4094) Fix importance labels for Kafka Server config

    [ https://issues.apache.org/jira/browse/KAFKA-4094 ]


    Abhi deleted comment on KAFKA-4094:
    -----------------------------

was (Author: JIRAUSER305362):
Hi [~jkreps] 
Can you describe this issue more and also mention which component it belongs to?

As per my understanding, you need the server configs like:- 

HIGH - broker.id, log.dirs, num.partitions

MEDIUM - log.segment.bytes, log.cleanup.policy

LOW -  message.max.bytes, replica.fetch.max.bytes

> 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)