[KAFKA-9851] Revoking Connect tasks due to connectivity issues should also clear running assignment - ASF JIRA

Agile Board

Attach files

Attach Screenshot

Voters

Watch issue

Watchers

Create sub-task

Link

Clone

Update Comment Author

Replace String in Comment

Update Comment Visibility

Delete Comments

XML

Word

Printable

JSON

Details

Type: Bug
Status: Resolved
Priority: Major
Resolution: Fixed
Affects Version/s: None
Fix Version/s: 2.3.2, 2.6.0, 2.4.2, 2.5.1
Component/s: connect
Labels:
None

Description

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.