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

Reducing number of tasks for connector causes deleted tasks to show as UNASSIGNED

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 2.0.0, 2.0.1, 2.1.0, 2.2.0, 2.1.1, 2.3.0, 2.2.1, 2.2.2, 2.4.0, 2.3.1
    • 2.3.2, 2.6.0, 2.4.2, 2.5.1
    • connect
    • None

    Description

      If a connector is successfully created with t1 running tasks and then reconfigured to use t1 - n tasks (where t1 and n are both whole numbers and n is strictly less than t1), the connector should then list t1 - n total tasks in its status (which can be queried via the /connectors/:name:/status endpoint or the /connectors endpoint with the expand URL query parameter set to status).

      However, the connector will instead continue to list t1 total tasks in its status, with n of them being listed as UNASSIGNED and the remaining t1 - n of them being listed as STARTED.

      This is because the only time a task status is removed from the status backing store (as opposed to simply being updated to UNASSIGNED) is when its connector is deleted. See relevant code snippets from the AbstractHerder and DistributedHerder classes.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            ChrisEgerton Chris Egerton
            ChrisEgerton Chris Egerton
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment