You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Konstantine Karantasis (Jira)" <ji...@apache.org> on 2020/06/06 00:37:00 UTC
[jira] [Resolved] (KAFKA-9851) Revoking Connect tasks due to
connectivity issues should also clear running assignment
[ https://issues.apache.org/jira/browse/KAFKA-9851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konstantine Karantasis resolved KAFKA-9851.
-------------------------------------------
Resolution: Fixed
> Revoking Connect tasks due to connectivity issues should also clear running assignment
> --------------------------------------------------------------------------------------
>
> Key: KAFKA-9851
> URL: https://issues.apache.org/jira/browse/KAFKA-9851
> Project: Kafka
> Issue Type: Bug
> Reporter: Konstantine Karantasis
> Assignee: Konstantine Karantasis
> Priority: Major
> Fix For: 2.3.2, 2.6.0, 2.4.2, 2.5.1
>
>
> https://issues.apache.org/jira/browse/KAFKA-9184 fixed an issue with workers continuing to run tasks even after they'd lose connectivity with the broker coordinator and they'd detect that they are out of the group.
>
> However, because the revocation of tasks in this case is voluntary and does not come with an explicit assignment (containing revoked tasks) from the leader worker, the worker that quits running its tasks due to connectivity issues needs to also clear its running task assignment snapshot.
> This will allow for proper restart of the stopped tasks after the worker rejoins the group when connectivity returns and get assigned the same connectors or tasks.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)