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

Posted to issues@flink.apache.org by "Thorne (Jira)" <ji...@apache.org> on 2024/06/24 03:29:00 UTC

[jira] [Updated] (FLINK-35674) MySQL connector may cause deadlock issues when searching for binlog timestamps

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

Thorne updated FLINK-35674:
---------------------------
    Description: 
When a task is started by multiple mysql connector timestamp start mode at the same time, when searching for binlog timestamp, there will be task blocking problem, which may cause source to be unable to obtain data all the time. 

 

  was:When a task is started by multiple mysql connector timestamp start mode at the same time, when searching for binlog timestamp, there will be task blocking problem, which may cause source to be unable to obtain data all the time. 


> MySQL connector may cause deadlock issues when searching for binlog timestamps
> ------------------------------------------------------------------------------
>
>                 Key: FLINK-35674
>                 URL: https://issues.apache.org/jira/browse/FLINK-35674
>             Project: Flink
>          Issue Type: Bug
>          Components: Flink CDC
>    Affects Versions: cdc-3.1.1
>         Environment: flink-cdc-3.1.x
>            Reporter: Thorne
>            Priority: Blocker
>             Fix For: cdc-3.2.0
>
>         Attachments: A7AE0D63-365D-4572-B63D-96DF5F096BF9.png, BF180441-9C61-40eb-B07C-A11F8BCEC2D0.png, FBA32597-8783-4678-B391-E450148C1B30.png
>
>
> When a task is started by multiple mysql connector timestamp start mode at the same time, when searching for binlog timestamp, there will be task blocking problem, which may cause source to be unable to obtain data all the time. 
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)