[ 
https://issues.apache.org/jira/browse/KAFKA-18222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18127207#comment-18127207
 ] 

Amrit Sarkar commented on KAFKA-18222:
--------------------------------------

Hi [~chia7712], this looks like the same root cause as KAFKA-19552, which was 
filed later. I reproduced it on current trunk with a {{@ClusterTest}} (isolated 
and combined KRaft):

||Where {{unclean.leader.election.enable=true}} is set||describeConfigs 
reports||Unclean election||
|broker {{server.properties}} only|true|*no*|
|broker {{server.properties}} + controller {{server.properties}}|true|yes|
|cluster-level dynamic config|true|yes|
|per-broker dynamic config ({{--entity-name 0}})|true|*no*|

The per-broker dynamic case is worth calling out in the docs too, since 
{{ConfigurationControlManager#currentControllerConfig}} only reads the 
controller's own node id.

Hi [~mingdaoy], are you still working on this? If not, I'm happy to send the 
docs PR (covering both the static and per-broker dynamic cases) and would ask 
for the ticket to be reassigned.


> broker-level unclean.leader.election.enable is useless
> ------------------------------------------------------
>
>                 Key: KAFKA-18222
>                 URL: https://issues.apache.org/jira/browse/KAFKA-18222
>             Project: Kafka
>          Issue Type: Improvement
>            Reporter: Chia-Ping Tsai
>            Assignee: Mingdao Yang
>            Priority: Minor
>
> The responsibility for conducting unclean leader elections now resides with 
> the controller. Therefore, we should update the documentation to inform users 
> that setting unclean.leader.election.enable in broker properties is 
> ineffective in KRaft. Instead, they should configure the controller 
> properties accordingly.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to