Uploaded image for project: 'Flume'
  1. Flume
  2. FLUME-3274

KafkaSource and JMSSource can get stuck at startup connection exception

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Won't Fix
    • None
    • None
    • None
    • None

    Description

      This problem can happen in sources that are derived from BasicSourceSemantics. BasicSourceSemantics at startup if an exception occurs, it stores it. This behavior only makes sense if the start only throws an exception for unrecoverable configuration problems. Both KafkaSource and JMSSource try to connect to a Kafka or JMS server at startup, if the server is not available the flume agent needs to be restarted. They both can recover after connection errors after a successful startup.
      The start() should only throw an exception for unrecoverable problems.
      We need to make sure that the reconnect mechanism is safe and even if there is some configuration problem it does not start a DOS attack.

      Attachments

        Activity

          People

            emajor Endre Major
            emajor Endre Major
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: