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/12/06 00:35:00 UTC
[jira] [Updated] (KAFKA-6299) Fix AdminClient error handling when
metadata changes
[ https://issues.apache.org/jira/browse/KAFKA-6299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Colin P. McCabe updated KAFKA-6299:
-----------------------------------
Description:
* AdminClient should retry requests for which the controller has changed
* Fix an issue where AdminClient requests might not get a security exception, even when a metadata fetch fails with an authorization exception.
* Fix a possible issue where AdminClient might leak a socket after the timeout expires on a hard close, if a very narrow race condition is hit
was:
* AdminClient should retry requests for which the controller or partition leader has changed
* Fix an issue where AdminClient requests might not get a security exception, even when a metadata fetch fails with an authorization exception.
* Fix a possible issue where AdminClient might leak a socket after the timeout expires on a hard close, if a very narrow race condition is hit
> Fix AdminClient error handling when metadata changes
> ----------------------------------------------------
>
> Key: KAFKA-6299
> URL: https://issues.apache.org/jira/browse/KAFKA-6299
> Project: Kafka
> Issue Type: Bug
> Reporter: Colin P. McCabe
> Assignee: Colin P. McCabe
>
> * AdminClient should retry requests for which the controller has changed
> * Fix an issue where AdminClient requests might not get a security exception, even when a metadata fetch fails with an authorization exception.
> * Fix a possible issue where AdminClient might leak a socket after the timeout expires on a hard close, if a very narrow race condition is hit
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)