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

KafkaConnect: DistributedHerder shouldn't wait forever to read configs after rebalance

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 0.10.0.0
    • Component/s: None
    • Labels:
      None

      Description

      Right now, the handleRebalance code calls readConfigToEnd with timeout of MAX_INT if it isn't the leader.

      The normal workerSyncTimeoutMs is probably sufficient.

      At least this allows a worker to time-out, get back to the tick() loop and check the "stopping" flag to see if it should shut down, to prevent it from hanging forever.

      It doesn't resolve the question of what we should do with a worker that repeatedly fails to read configuration.

        Attachments

          Activity

            People

            • Assignee:
              gwenshap Gwen Shapira
              Reporter:
              gwenshap Gwen Shapira
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: