Uploaded image for project: 'Kafka'
  1. Kafka
  2. KAFKA-9851

Revoking Connect tasks due to connectivity issues should also clear running assignment

    XMLWordPrintableJSON

    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: KafkaConnect
    • 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. 

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                kkonstantine Konstantine Karantasis
                Reporter:
                kkonstantine Konstantine Karantasis
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: