Flink CDC Issue Import created FLINK-34794:
----------------------------------------------

             Summary: [Bug] if splitTable method execute fast than getNext, job 
will be blocked
                 Key: FLINK-34794
                 URL: https://issues.apache.org/jira/browse/FLINK-34794
             Project: Flink
          Issue Type: Bug
          Components: Flink CDC
            Reporter: Flink CDC Issue Import


### Search before asking

- [X] I searched in the 
[issues|https://github.com/ververica/flink-cdc-connectors/issues) and found 
nothing similar.


### Flink version
[e49e22065fdd6f1026db76f81bd8ed38e81ef173|https://github.com/apache/flink-cdc/commit/e49e22065fdd6f1026db76f81bd8ed38e81ef173]

### Flink CDC version
[e49e22065fdd6f1026db76f81bd8ed38e81ef173|https://github.com/apache/flink-cdc/commit/e49e22065fdd6f1026db76f81bd8ed38e81ef173]

### Database and its version

mysql:  mysql 8.0.27

### Minimal reproduce step

add `Thread.sleep(10000)` before MySqlSnapshotSplitAssigner.getNext().  
lock.wait will not be notify any more, and it will wait forever.

### What did you expect to see?

job can execute normally

### What did you see instead?

nothing

### Anything else?

On MysqlCDC job start,  the method splitTable() &&  getNext(] from 
MySqlSnapshotSplitAssigner will be execute asynchronously, the two method use 
one lock, and depend on the order of execution。Under special circumstances,  
the job does not perform as expected

### Are you willing to submit a PR?

- [x] I'm willing to submit a PR!

---------------- Imported from GitHub ----------------
Url: https://github.com/apache/flink-cdc/issues/2187
Created by: [y0908105023|https://github.com/y0908105023]
Labels: bug, 
Assignee: [y0908105023|https://github.com/y0908105023]
Created at: Wed Jun 07 11:37:46 CST 2023
State: open




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

Reply via email to