You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "michaelxiang (Jira)" <ji...@apache.org> on 2022/06/23 02:48:00 UTC

[jira] [Reopened] (FLINK-28205) memory leak in the timing refresh of the jdbc-connector

     [ https://issues.apache.org/jira/browse/FLINK-28205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

michaelxiang reopened FLINK-28205:
----------------------------------

I changed the language

> memory leak in the timing refresh of the jdbc-connector
> -------------------------------------------------------
>
>                 Key: FLINK-28205
>                 URL: https://issues.apache.org/jira/browse/FLINK-28205
>             Project: Flink
>          Issue Type: Bug
>          Components: Connectors / JDBC
>    Affects Versions: 1.15.0, 1.13.6, 1.14.5
>            Reporter: michaelxiang
>            Priority: Major
>
> Bug position: org.apache.flink.connector.jdbc.internal.JdbcBatchingOutputFormat.scheduler
> When writing with the jdbc-connector, the RuntimeException thrown by the scheduled thread to process the flush record is caught, this will cause the flink task to not fail out until new data arrives. So, during this time, the scheduled thread will continue to wrap the previous flushException by creating a RuntimeException. For each flushException, the object reference cannot be released and cannot be reclaimed by the GC, resulting in a memory leak.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)