[ 
https://issues.apache.org/jira/browse/KAFKA-9683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Cheng Tan updated KAFKA-9683:
-----------------------------
    Summary: [KIP-576] Support dynamic update of 
fetch.max.bytes/failed.authentication.delay/replica.fetch.response.max.bytes/replica.fetch.wait.max.ms/follower.replication.throttled.replicas/leader.replication.throttled.replicas
  (was: KIP-576 Support dynamic update of 
fetch.max.bytes/failed.authentication.delay/replica.fetch.response.max.bytes/replica.fetch.wait.max.ms/follower.replication.throttled.replicas/leader.replication.throttled.replicas)

> [KIP-576] Support dynamic update of 
> fetch.max.bytes/failed.authentication.delay/replica.fetch.response.max.bytes/replica.fetch.wait.max.ms/follower.replication.throttled.replicas/leader.replication.throttled.replicas
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: KAFKA-9683
>                 URL: https://issues.apache.org/jira/browse/KAFKA-9683
>             Project: Kafka
>          Issue Type: Bug
>            Reporter: Cheng Tan
>            Priority: Major
>
> [KIP-226|https://cwiki.apache.org/confluence/display/KAFKA/KIP-226+-+Dynamic+Broker+Configuration]
>  added support for dynamic update of  broker configuration.  In this KIP, we 
> propose to extend the support to dynamic update of a group of new dynamic 
> broker configs below which will benefit the replication process.
> fetch.max.bytes
> failed.authentication.delay
> replica.fetch.response.max.bytes
> replica.fetch.wait.max.ms
> follower.replication.throttled.replicas
> leader.replication.throttled.replicas



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to