You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Maximilian Michels (Jira)" <ji...@apache.org> on 2020/03/12 12:40:00 UTC
[jira] [Commented] (FLINK-16573) Kinesis consumer does not properly
shutdown RecordFetcher threads
[ https://issues.apache.org/jira/browse/FLINK-16573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17057889#comment-17057889 ]
Maximilian Michels commented on FLINK-16573:
--------------------------------------------
Should add that this eventually causes the meta space to run out after many job restarts because the lingering threads prevent old classloaders to be garbage collected.
> Kinesis consumer does not properly shutdown RecordFetcher threads
> -----------------------------------------------------------------
>
> Key: FLINK-16573
> URL: https://issues.apache.org/jira/browse/FLINK-16573
> Project: Flink
> Issue Type: Bug
> Components: Connectors / Kinesis
> Affects Versions: 1.8.3, 1.9.2, 1.10.0
> Reporter: Maximilian Michels
> Assignee: Maximilian Michels
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.11.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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:
> {noformat}
> 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)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)