8000 Create conflict database.source.name in source/sink · Issue #12301 · risingwavelabs/risingwave · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Create conflict database.source.name in source/sink #12301

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
QuantumBear opened this issue Sep 14, 2023 · 3 comments
Open

Create conflict database.source.name in source/sink #12301

QuantumBear opened this issue Sep 14, 2023 · 3 comments
Assignees
@wcy-fdu
Labels
type/bug Type: Bug. Only for issues.
Milestone
release-2.5

Comments

@QuantumBear
Copy link
QuantumBear commented Sep 14, 2023 •
edited by StrikeW
Loading

Describe the bug

cdc source from mysql5, then sink to mysql 8. Fail to create sink.

(base) ➜  sql git:(main) ✗ psql -h myip  -p  31146  -d dev -U root < sink.sql
ERROR:  QueryError: internal error: failed to finish command: channel closed
(base) ➜  sql git:(main) ✗ psql -h myip  -p  31146  -d dev -U root < sink.sql
ERROR:  QueryError: internal error: Service unavailable: The cluster is starting or recovering

Error message/log

2023-09-14 06:25:05,562 ERROR [rw-dbz-engine-runner-6178] core.DbzCdcEngineRunner:55 - engine#6178 terminated with error. message: Unable to initialize and start connector's task class 'io.debezium.connector.mysql.MySqlConnectorTask' with config: {connector.class=io.debezium.connector.mysql.MySqlConnector, max.queue.size=8192, provide.transaction.metadata=false, include.schema.changes=false, decimal.handling.mode=string, offset.storage.file.filename=, converters=datetime, interval.handling.mode=string, datetime.type=com.risingwave.connector.cdc.debezium.converters.DatetimeTypeConverter, value.converter=org.apache.kafka.connect.json.JsonConverter, key.converter=org.apache.kafka.connect.json.JsonConverter, database.user=willing, offset.storage=com.risingwave.connector.cdc.debezium.internal.ConfigurableOffsetBackingStore, database.server.id=8571, time.precision.mode=adaptive_time_microseconds, database.server.name=RW_CDC_6178, offset.flush.timeout.ms=5000, offset.storage.risingwave.state.value={"sourcePartition":{"server":"RW_CDC_6178"},"sourceOffset":{"transaction_id":null,"ts_sec":1694599033,"file":"mysql-bin.000057","pos":8486973,"row":1,"server_id":1,"event":2}}, database.port=3306, offset.flush.interval.ms=60000, internal.key.converter=org.apache.kafka.connect.json.JsonConverter, database.hostname=172.30.10.10, database.password=********, name=172.30.10.10:3306:willing_base.scrm_progress, internal.value.converter=org.apache.kafka.connect.json.JsonConverter, max.batch.size=1024, table.include.list=willing_base.scrm_progress, snapshot.mode=schema_only_recovery, database.history=io.debezium.relational.history.MemoryDatabaseHistory, database.include.list=willing_base}
java.lang.RuntimeException: Unable to register the MBean 'debezium.mysql:type=connector-metrics,context=schema-history,server=RW_CDC_6178'
 at io.debezium.metrics.Metrics.register(Metrics.java:108) ~[debezium-core-1.9.7.Final.jar:1.9.7.Final]
 at io.debezium.relational.history.DatabaseHistoryMetrics.started(DatabaseHistoryMetrics.java:95) ~[debezium-core-1.9.7.Final.jar:1.9.7.Final]
 at io.debezium.relational.history.AbstractDatabaseHistory.start(AbstractDatabaseHistory.java:82) ~[debezium-core-1.9.7.Final.jar:1.9.7.Final]
 at io.debezium.relational.HistorizedRelationalDatabaseSchema.<init>(HistorizedRelationalDatabaseSchema.java:42) ~[debezium-core-1.9.7.Final.jar:1.9.7.Final]
 at io.debezium.connector.mysql.MySqlDatabaseSchema.<init>(MySqlDatabaseSchema.java:93) ~[debezium-connector-mysql-1.9.7.Final.jar:1.9.7.Final]
 at io.debezium.connector.mysql.MySqlConnectorTask.start(MySqlConnectorTask.java:93) ~[debezium-connector-mysql-1.9.7.Final.jar:1.9.7.Final]
 at io.debezium.connector.common.BaseSourceTask.start(BaseSourceTask.java:133) ~[debezium-core-1.9.7.Final.jar:1.9.7.Final]
 at io.debezium.embedded.EmbeddedEngine.run(EmbeddedEngine.java:760) [debezium-embedded-1.9.7.Final.jar:1.9.7.Final]
 at io.debezium.embedded.ConvertingEngineBuilder$2.run(ConvertingEngineBuilder.java:192) [debezium-embedded-1.9.7.Final.jar:1.9.7.Final]
 at com.risingwave.connector.source.core.DbzCdcEngine.run(DbzCdcEngine.java:54) [risingwave-connector-service-1.0-SNAPSHOT.jar:?]
 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) [?:?]
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:?]
 at java.lang.Thread.run(Thread.java:829) [?:?]
Caused by: java.lang.InterruptedException: sleep interrupted
 at java.lang.Thread.sleep(Native Method) ~[?:?]
 at io.debezium.util.Metronome$1.pause(Metronome.java:57) ~[debezium-core-1.9.7.Final.jar:1.9.7.Final]
 at io.debezium.metrics.Metrics.register(Metrics.java:96) ~[debezium-core-1.9.7.Final.jar:1.9.7.Final]
 ... 12 more



### To Reproduce

_No response_


### Expected behavior

_No response_


### How did you deploy RisingWave?

_No response_


### The version of RisingWave

dev=> select version();
version

PostgreSQL 9.5-RisingWave-1.2.0 (f27f085)
(1 row)


### Additional context

_No response_
@QuantumBear QuantumBear added the type/bug Type: Bug. Only for issues. label Sep 14, 2023
@github-actions github-actions bot added this to the release-1.3 milestone Sep 14, 2023
@StrikeW
Copy link
Contributor
StrikeW commented Sep 14, 2023

After checking the logs of the meta node, we found that the cluster continuously triggers recovery state, so it can't process the DDL request. Due to the incomplete log, the root cause of recovery cannot be decided yet. There are many gRPC errors in the log of meta and the connector node sees many “Connection broken detected, stop the engine” message.

A new issue found in the log is recorded in #12313, we may fix the issue and see whether continuous recovery still occur.

@StrikeW StrikeW self-assigned this Oct 9, 2023
@hzxa21 hzxa21 modified the milestones: release-1.3, release-1.4 Oct 10, 2023
@hzxa21
Copy link
Collaborator
hzxa21 commented Nov 8, 2023

@StrikeW #12313 is marked as completed. Can you confirm that whether this issue is fixed?

@fuyufjh fuyufjh closed this as completed Nov 9, 2023
@BugenZhao
Copy link
Member

Some users are still encountering this in v2.3.0 after creating a considerable amount of tables from the same CDC source. The error message is also Unable to register the MBean.

@BugenZhao BugenZhao reopened this May 8, 2025
@BugenZhao BugenZhao assigned wcy-fdu and unassigned StrikeW May 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@wcy-fdu wcy-fdu

Labels
type/bug Type: Bug. Only for issues.
Projects
None yet
Milestone
release-2.5
Development

No branches or pull requests
6 participants
@QuantumBear @hzxa21 @StrikeW @fuyufjh @BugenZhao @wcy-fdu
0