You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Jason Gustafson (Jira)" <ji...@apache.org> on 2019/11/16 17:57:00 UTC

[jira] [Created] (KAFKA-9198) StopReplica handler should complete pending purgatory operations

Jason Gustafson created KAFKA-9198:
--------------------------------------

             Summary: StopReplica handler should complete pending purgatory operations
                 Key: KAFKA-9198
                 URL: https://issues.apache.org/jira/browse/KAFKA-9198
             Project: Kafka
          Issue Type: Bug
            Reporter: Jason Gustafson
            Assignee: Jason Gustafson


When a reassignment completes, the current leader may need to be shutdown with a StopReplica request. It may still have fetch/produce requests in purgatory when this happens. We do not have logic currently to force completion of these requests which means they are doomed to eventually timeout. This is mostly an issue for produce requests which use the default request timeout of 30s.



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

Re: [jira] [Created] (KAFKA-9198) StopReplica handler should complete pending purgatory operations

Posted by KUN DU <du...@gmail.com>.
Looks like it is the same issue as
https://issues.apache.org/jira/browse/KAFKA-8571
And there is a PR for that https://github.com/apache/kafka/pull/7069

Jason Gustafson (Jira) <ji...@apache.org> 于2019年11月16日周六 上午9:57写道:

> Jason Gustafson created KAFKA-9198:
> --------------------------------------
>
>              Summary: StopReplica handler should complete pending
> purgatory operations
>                  Key: KAFKA-9198
>                  URL: https://issues.apache.org/jira/browse/KAFKA-9198
>              Project: Kafka
>           Issue Type: Bug
>             Reporter: Jason Gustafson
>             Assignee: Jason Gustafson
>
>
> When a reassignment completes, the current leader may need to be shutdown
> with a StopReplica request. It may still have fetch/produce requests in
> purgatory when this happens. We do not have logic currently to force
> completion of these requests which means they are doomed to eventually
> timeout. This is mostly an issue for produce requests which use the default
> request timeout of 30s.
>
>
>
> --
> This message was sent by Atlassian Jira
> (v8.3.4#803005)
>