[
https://issues.apache.org/jira/browse/KAFKA-16368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17924203#comment-17924203
]
Divij Vaidya commented on KAFKA-16368:
--------------------------------------
Changes implemented as part of this Jira (also updated in KIP):
# segment.bytes / log.segment.bytes
# num.recovery.threads.per.data.dir
# linger.ms
# message.timestamp.after.max.ms / log.message.timestamp.after.max.ms
# remote.log.manager.copier.thread.pool.size
# remote.log.manager.expiration.thread.pool.size
# remote.log.manager.thread.pool.size
Punting the leftover ones in the KIP to a new Jira targeted for 5.0
> Change constraints and default values for various configurations
> ----------------------------------------------------------------
>
> Key: KAFKA-16368
> URL: https://issues.apache.org/jira/browse/KAFKA-16368
> Project: Kafka
> Issue Type: Improvement
> Reporter: Divij Vaidya
> Assignee: Jason Taylor
> Priority: Major
> Labels: breaking, kip
> Fix For: 4.0.0
>
>
> This Jira is a parent item to track all the defaults and/or constraints that
> we would like to change with Kafka 4.0. This Jira will be associated with a
> KIP.
> Currently, we are gathering feedback from the community on the configurations
> that don't have sane defaults.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
