Fixed: apache/flink#42905 (release-1.9 - a9bbcc6)

[Flink CI <fl...@foxmail.com>]

|  [

apache

/

flink

](https://travis-ci.org/apache/flink)  
---  
  
![branch icon](https://s3.amazonaws.com/travis-email-
assets/branch.png)[release-1.9](https://github.com/apache/flink/tree/release-1.9)  
  
|

![build hasfailed](https://s3.amazonaws.com/travis-email-assets/status-
passed.png)

[Build #42905 fixed](https://travis-ci.org/apache/flink/builds/663030997)

![arrow to build time](https://s3.amazonaws.com/travis-email-assets/success-
arrow.png)

![clock icon](https://s3.amazonaws.com/travis-email-assets/time.png)4 hrs, 15
mins, 42 secs  
  
---  
  
![Maximilian Michels
avatar](https://secure.gravatar.com/avatar/d7027b0c31db77a64f2143c11cda37ca.jpg)Maximilian
Michels

[a9bbcc6 CHANGESET
->](https://github.com/apache/flink/compare/366cdc7d7d90...a9bbcc69e5bc)  
  
[FLINK-16573] Ensure Kinesis RecordFetcher threads shutdown on cancel  
  
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)  
```