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

Posted to jira@kafka.apache.org by "Jason Gustafson (Jira)" <ji...@apache.org> on 2020/12/10 17:26:00 UTC

[jira] [Resolved] (KAFKA-10677) Complete fetches in purgatory immediately after raft leader resigns

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

Jason Gustafson resolved KAFKA-10677.
-------------------------------------
    Resolution: Fixed

> Complete fetches in purgatory immediately after raft leader resigns
> -------------------------------------------------------------------
>
>                 Key: KAFKA-10677
>                 URL: https://issues.apache.org/jira/browse/KAFKA-10677
>             Project: Kafka
>          Issue Type: Sub-task
>            Reporter: Jason Gustafson
>            Assignee: dengziming
>            Priority: Major
>
> The current logic does not complete fetches in purgatory immediately after the leader has resigned. The idea was that there was no point in doing so until the election had completed because clients would just have to retry. However, the fetches in purgatory might correspond to requests from other voters, so the concern is that this might delay a leader election. For example, the voter might be trying to send a Vote request on the same socket that is blocking on a pending Fetch.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)