Debezium connector issue - Connector is not getting connected automatically when postgres database server is getting stop and then start again [DBZ-8322]
- Dominant language
- HTML
- Stars
- 6
- Forks
- 8
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 1
Description
Migrated from [DBZ-8322](https://issues.redhat.com/browse/DBZ-8322)
We are using debezium connector to connect postgress database and process the operation to azure function.
When I will stop database server and start again or restart it, connector is loosing connection and then its not connecting automatically, so we are calling api to update connector with same details, but I want to avoid this.
Is there anyway in connector details to say retry and reconnect database?
Atleast retry for next 1 hour when it started getting failed?
Contributor guide
Research direction
No repository files, tests, or entry points are named. Start by reproducing the connector behavior while stopping and restarting the PostgreSQL server, then inspect the connector configuration and its retry or reconnect behavior. Done means the connector reconnects automatically after the database returns without an API update.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, postgresql
- Domain
- cloud, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100