You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Flink CDC Issue Import (Jira)" <ji...@apache.org> on 2024/03/20 09:23:00 UTC
[jira] [Created] (FLINK-34797) [Bug] Debezium's database.server.name property should not be hard-coded
Flink CDC Issue Import created FLINK-34797:
----------------------------------------------
Summary: [Bug] Debezium's database.server.name property should not be hard-coded
Key: FLINK-34797
URL: https://issues.apache.org/jira/browse/FLINK-34797
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
1.17.1
### Flink CDC version
2.3.0
### Database and its version
Postgres
### Minimal reproduce step
Running multiple postgres CDC connectors in one JVM process; this will trigger warnings about conflicting MBean names for the Debezium metrics beans, caused by hard-coding the logical server name property to one constant value in [here|https://github.com/ververica/flink-cdc-connectors/blob/master/flink-connector-postgres-cdc/src/main/java/com/ververica/cdc/connectors/postgres/PostgreSQLSource.java#L157). As this name also is used to disambiguate the MBean names, it must be unique across connectors running on the same JVM (and should be unique globally anyways].
### What did you expect to see?
There should be a connector option for specifying the Debezium `database.server.name` property.
### What did you see instead?
Conflicting MBean names
### Anything else?
_No response_
### 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/2235
Created by: [gunnarmorling|https://github.com/gunnarmorling]
Labels: bug,
Created at: Mon Jun 26 17:07:25 CST 2023
State: open
--
This message was sent by Atlassian Jira
(v8.20.10#820010)