Uploaded image for project: 'Flink'
  1. Flink
  2. FLINK-16573

Kinesis consumer does not properly shutdown RecordFetcher threads

    XMLWordPrintableJSON

    Details

      Description

      The threads may not shut down correctly because they do not check for the running flag in the inner loops. The threads also do not get interrupted because they are not connected to the main task thread.

      These threads keep lingering around after the job has shut down:

      Thread 23168: (state = BLOCKED)
       - java.lang.Object.wait(long) @bci=0 (Compiled frame; information may be imprecise)
       - org.apache.flink.streaming.connectors.kinesis.util.RecordEmitter.emitRecords() @bci=140, line=209 (Compiled frame)
       - org.apache.flink.streaming.connectors.kinesis.util.RecordEmitter.run() @bci=18, line=177 (Interpreted frame)
       - java.lang.Thread.run() @bci=11, line=748 (Compiled frame)
      

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                mxm Maximilian Michels
                Reporter:
                mxm Maximilian Michels
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 20m
                  20m