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

Worker can die if unable to write new session key

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

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 2.4.2, 2.5.2, 2.8.0, 2.7.1, 2.6.2, 3.0.0
    • 2.5.2, 2.8.0, 2.7.1, 2.6.2, 3.0.0
    • KafkaConnect
    • None

    Description

      If a distributed worker is unable to write (and then read back) a new session key to the config topic, an uncaught exception will be thrown from its herder's tick thread, killing the worker.

      See https://github.com/apache/kafka/blob/8da65936d7fc53d24c665c0d01893d25a430933b/connect/runtime/src/main/java/org/apache/kafka/connect/runtime/distributed/DistributedHerder.java#L366-L369

      One way we can handle this case by forcing a read to the end of the config topic whenever an attempt to write a new session key to the config topic fails.

      Attachments

        Activity

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

          People

            ChrisEgerton Chris Egerton
            ChrisEgerton Chris Egerton
            Randall Hauch Randall Hauch
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment