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

DistributedHerder thread can die because of connector & task lifecycle exceptions

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 0.10.1.0
    • connect
    • None

    Description

      As one example, there isn't exception handling in DistributedHerder.startConnector() or the call-chain for it originating in the tick() on the herder thread, and it can throw an exception because of a bad class name in the connector config. (report of issue in wild: https://groups.google.com/d/msg/confluent-platform/EnleFnXpZCU/3B_gRxsRAgAJ)

      Attachments

        Issue Links

          is related to

          Improvement - An improvement or enhancement to an existing feature or task. KAFKA-14670 Refactor connect plugins to be called from wrapper classes

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • In Progress
          relates to

          Bug - A problem which impairs or prevents the functions of the product. KAFKA-3054 Connect Herder fail forever if sent a wrong connector config or task config

          • Blocker - Blocks development and/or testing work, production could not run
          • Resolved
          links to

          Web Link GitHub Pull Request #1745

          Web Link GitHub Pull Request #1778

          Activity

            People

              shikhar Shikhar Bhushan
              shikhar Shikhar Bhushan
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: