[
https://issues.apache.org/jira/browse/KAFKA-2691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14983605#comment-14983605
]
ASF GitHub Bot commented on KAFKA-2691:
---------------------------------------
GitHub user hachikuji opened a pull request:
https://github.com/apache/kafka/pull/394
KAFKA-2691: Improve handling of authorization failure during metadata
refresh
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/hachikuji/kafka KAFKA-2691
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/394.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #394
----
commit 722980095636f8d0f633aa1f40a6aa5736facdbe
Author: Jason Gustafson <ja...@confluent.io>
Date: 2015-10-30T23:40:00Z
KAFKA-2691: Improve handling of authorization failure during metadata
refresh
----
> Improve handling of authorization failure during metadata refresh
> -----------------------------------------------------------------
>
> Key: KAFKA-2691
> URL: https://issues.apache.org/jira/browse/KAFKA-2691
> Project: Kafka
> Issue Type: Sub-task
> Components: security
> Reporter: Ismael Juma
> Assignee: Jason Gustafson
> Fix For: 0.9.0.0
>
>
> There are two problems, one more severe than the other:
> 1. The consumer blocks indefinitely if there is non-transient authorization
> failure during metadata refresh due to KAFKA-2391
> 2. We get a TimeoutException instead of an AuthorizationException in the
> producer for the same case
> If the fix for KAFKA-2391 is to add a timeout, then we will have issue `2` in
> both producer and consumer.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
