[
https://issues.apache.org/jira/browse/KAFKA-5658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colin P. McCabe updated KAFKA-5658:
-----------------------------------
Description: The AdminClient does not properly clear calls from the
callsInFlight structure. Later, in an effort to clear the lingering call
objects, it closes the connection they are associated with. This disrupts new
incoming calls, which then get {{java.util.concurrent.ExecutionException:
org.apache.kafka.common.errors.BrokerNotAvailableException}}. (was: if i
create an admin client and let it sit unused for some amount of time, then
attempt to use it i will get the following
{noformat}
java.util.concurrent.ExecutionException:
org.apache.kafka.common.errors.BrokerNotAvailableException
{noformat}
even though the broker is up. if before each usage of adminclient i create a
new admin client i do not see the same behavior.)
> Fix AdminClient request timeout handling bug resulting in continual
> BrokerNotAvailableExceptions
> ------------------------------------------------------------------------------------------------
>
> Key: KAFKA-5658
> URL: https://issues.apache.org/jira/browse/KAFKA-5658
> Project: Kafka
> Issue Type: Bug
> Reporter: dan norwood
> Assignee: Colin P. McCabe
> Priority: Critical
> Labels: reliability
> Fix For: 0.11.0.1
>
>
> The AdminClient does not properly clear calls from the callsInFlight
> structure. Later, in an effort to clear the lingering call objects, it
> closes the connection they are associated with. This disrupts new incoming
> calls, which then get {{java.util.concurrent.ExecutionException:
> org.apache.kafka.common.errors.BrokerNotAvailableException}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
