You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2019/07/15 02:05:00 UTC
[jira] [Updated] (FLINK-13253) Deadlock may occur in
JDBCUpsertOutputFormat
[ https://issues.apache.org/jira/browse/FLINK-13253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated FLINK-13253:
-----------------------------------
Labels: pull-request-available (was: )
> Deadlock may occur in JDBCUpsertOutputFormat
> --------------------------------------------
>
> Key: FLINK-13253
> URL: https://issues.apache.org/jira/browse/FLINK-13253
> Project: Flink
> Issue Type: Bug
> Components: Connectors / JDBC
> Reporter: Jingsong Lee
> Assignee: Jingsong Lee
> Priority: Major
> Labels: pull-request-available
>
> In close, it await the flush scheduler terminal, but it hold the lock of JDBCUpsertOutputFormat instance, maybe the async thread is waiting for this lock in the flush method, so there might be a deadlock here.
> First, it should not await scheduler terminal, because it has flushed all data to jdbc, what we should do is let async thread quit.
> Second, we should add lock outside the closed check in the flusher, in this way, we can ensure async thread secure exiting.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)