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

PR '#6850' fix issue 'KAFKA-8449', but lead to restart all cached tasks, which conflict to the motivation of incremental cooperative rebalancing.

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Patch Available
    • Blocker
    • Resolution: Unresolved
    • 2.3.0
    • None
    • connect
    • None

    Description

      Recently, we are testing Kafka Connect 2.3.0, checking the incremental cooperative rebalancing mechanism.

       

      We found that when new connector was putted via REST endpoint, Kafka Connect 2.3.0 will restart all cached tasks;

      And the issuse is  'KAFKA-8449', the PR is '#6850';

       

      So, the result is, new connector putted will lead to all cached tasks restarted, which conflict to the motivation of incremental cooperative rebalancing. 

       

      Should it just restart the new reconfigurated connector or tasks, not all cached ones?

      And I have made a PR, please check it out,  '#7348'

      Attachments

        Activity

          People

            Unassigned Unassigned
            HeryLong HeryLong
            Konstantine Karantasis Konstantine Karantasis
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated: