You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "Vikas Singh (JIRA)" <ji...@apache.org> on 2019/05/25 00:25:00 UTC

[jira] [Resolved] (KAFKA-8341) AdminClient should retry coordinator lookup after NOT_COORDINATOR error

     [ https://issues.apache.org/jira/browse/KAFKA-8341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vikas Singh resolved KAFKA-8341.
--------------------------------
    Resolution: Fixed

fixed in commit 46a02f3231cd6d340c622636159b9f59b4b3cb6e

> AdminClient should retry coordinator lookup after NOT_COORDINATOR error
> -----------------------------------------------------------------------
>
>                 Key: KAFKA-8341
>                 URL: https://issues.apache.org/jira/browse/KAFKA-8341
>             Project: Kafka
>          Issue Type: Bug
>            Reporter: Jason Gustafson
>            Assignee: Vikas Singh
>            Priority: Major
>
> If a group operation (e.g. DescribeGroup) fails because the coordinator has moved, the AdminClient should lookup the coordinator before retrying the operation. Currently we will either fail or just retry anyway. This is similar in some ways to controller rediscovery after getting NOT_CONTROLLER errors.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)