[
https://issues.apache.org/jira/browse/KAFKA-16232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Luke Chen reassigned KAFKA-16232:
---------------------------------
Assignee: Kuan-Po Tseng
> kafka hangs forever in the starting process if the authorizer future is not
> returned
> ------------------------------------------------------------------------------------
>
> Key: KAFKA-16232
> URL: https://issues.apache.org/jira/browse/KAFKA-16232
> Project: Kafka
> Issue Type: Improvement
> Affects Versions: 3.6.1
> Reporter: Luke Chen
> Assignee: Kuan-Po Tseng
> Priority: Major
>
> For security reason, during broker startup, we will wait until all ACL
> entries loaded before starting serving requests. But recently, we
> accidentally set standardAuthorizer to ZK broker, and then, the broker never
> enters RUNNING state because it's waiting for the standardAuthorizer future
> completion. Of course this is a human error to set the wrong configuration,
> but it'd be better we could handle this case better. Suggestions:
> 1. set timeout for authorizer future waiting (how long is long enough?)
> 2. add logs before and after future waiting, to allow admin to know we're
> waiting for the authorizer future.
> We can start with (2), and thinking about (1) later.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
