[jira] [Commented] (KAFKA-13156) KafkaStatusBackingStore making incorrect assumption about order of task and connector delete events

["Sagar Rao (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KAFKA-13156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17722367#comment-17722367 ] 

Sagar Rao commented on KAFKA-13156:
-----------------------------------

hey [~ChrisEgerton] , I assigned this to myself ( I hope that's ok). I see it has been open for a while. I can send out a PR for this.

> KafkaStatusBackingStore making incorrect assumption about order of task and connector delete events
> ---------------------------------------------------------------------------------------------------
>
>                 Key: KAFKA-13156
>                 URL: https://issues.apache.org/jira/browse/KAFKA-13156
>             Project: Kafka
>          Issue Type: Bug
>          Components: KafkaConnect
>            Reporter: Nigel Liang
>            Assignee: Sagar Rao
>            Priority: Minor
>
> When a connector remove message is read from the status topic, `KafkaStatusBackingStore` removes both the connector and associated tasks from its connector and tasks cache. However, due to potentially partitioned nature of the status topic, there is no guarantee about the order of delivery for the connector removal message and task status messages for the same connector. If the connector is rapidly removed and recreated, the status backing store may see the task running events before the connector removal, in which case the running tasks would be removed from the tasks cache.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)