apache / seatunnel

SeaTunnel is a next-generation super high-performance, distributed, massive data integration tool.
https://seatunnel.apache.org/
Apache License 2.0
7.99k stars 1.81k forks source link

[Bug] [mysql-cdc] slave server-id conflict #3731

Open hailin0 opened 1 year ago

hailin0 commented 1 year ago

Search before asking

What happened

submit job throws slave server-id conflict

SeaTunnel Version

dev

SeaTunnel Config

env {
    execution.parallelism = 1
    job.mode = "STREAMING"
    checkpoint.interval = 5000
}

source {
  MySQL-CDC {
      result_table_name = "fake"
      parallelism = 1
      port = 3306
      server-id = "5401"
      hostname = "localhost"
      username = "root"
      password = "123456"
      database-name = "test"
      table-name = "test"
      base-url = "jdbc:mysql://localhost:3306"
    }
}

sink {
    Console {
        source_table_name = "fake"
    }
}

Running Command

bin/seatunnel.sh -e local --config mysql_cdc_to_elasticsearch.conf

Error Exception

Caused by: com.github.shyiko.mysql.binlog.network.ServerException: A slave with the same server_uuid/server_id as this slave has connected to the master; the first event 'binlog.000005' at 157, the last event read from './binlog.000005' at 126, the last byte read from './binlog.000005' at 157.

Flink or Spark Version

No response

Java or Scala Version

No response

Screenshots

image

Are you willing to submit PR?

Code of Conduct

hailin0 commented 1 year ago

@ashulin

github-actions[bot] commented 1 year ago

This issue has been automatically marked as stale because it has not had recent activity for 30 days. It will be closed in next 7 days if no further activity occurs.

github-actions[bot] commented 1 year ago

This issue has been closed because it has not received response for too long time. You could reopen it if you encountered similar problems in the future.

github-actions[bot] commented 1 year ago

This issue has been closed because it has not received response for too long time. You could reopen it if you encountered similar problems in the future.

chaorongzhi commented 1 year ago

@ashulin

Has this issue been resolved?

hailin0 commented 3 months ago

Anyone willing to fix it?