Differences in Logical Replication Port Mechanisms Between GaussDB CDC and openGauss CDC (HA Port Issue)
- Dominant language
- Java
- Stars
- 9.7k
- Forks
- 2.4k
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 204
Description
### Search before asking
- [x] I had searched in the [feature](https://github.com/apache/seatunnel/issues?q=is%3Aissue+label%3A%22Feature%22) and found no similar feature requirement.
### Description
GaussDB CDC与 openGauss CDC 在逻辑复制端口机制上的差异(HA 端口问题)
报错信息(replication should connect HA port in thread_pool 和 the local listen ip and port is not for the gsql client)期望连接器能够支持 GaussDB 的双端口模式
### Usage Scenario
_No response_
### Related issues
_No response_
### Are you willing to submit a PR?
- [ ] Yes I am willing to submit a PR!
### Code of Conduct
- [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the reported GaussDB CDC connection errors involving the HA port, thread_pool, and local listen address. No source file, test, or entry point is named, so locate the CDC connector's connection configuration and existing openGauss port handling first. Done means the connector supports GaussDB's dual-port mode without rejecting the replication connection.
Written by the indexing model from the issue text.
Assessment
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100