You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Colin P. McCabe (JIRA)" <ji...@apache.org> on 2017/07/26 20:58:00 UTC
[jira] [Updated] (KAFKA-5658) Fix AdminClient request timeout
handling bug resulting in continual BrokerNotAvailableExceptions
[ https://issues.apache.org/jira/browse/KAFKA-5658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Colin P. McCabe updated KAFKA-5658:
-----------------------------------
Summary: Fix AdminClient request timeout handling bug resulting in continual BrokerNotAvailableExceptions (was: adminclient will stop working after some amount of time)
> 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
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)