Skip to content
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

Rebuild the cdc connector if it encounter upstream errors #14120

Closed
StrikeW opened this issue Dec 21, 2023 · 1 comment
Closed

Rebuild the cdc connector if it encounter upstream errors #14120

StrikeW opened this issue Dec 21, 2023 · 1 comment
Assignees
@StrikeW
Labels
type/feature
Milestone
release-1.7

Comments

@StrikeW
Copy link
Contributor

StrikeW commented Dec 21, 2023

Is your feature request related to a problem? Please describe.

IIRC we have implemented the logic to rebuild a connector when it goes wrong. To confirm whether it covers the cdc connector.

Describe the solution you'd like

No response

Describe alternatives you've considered

No response

Additional context

No response
@StrikeW StrikeW self-assigned this Dec 21, 2023
@github-actions github-actions bot added this to the release-1.6 milestone Dec 21, 2023
@StrikeW StrikeW modified the milestones: release-1.6, release-1.7 Jan 9, 2024
@StrikeW
Copy link
Contributor Author

StrikeW commented Jan 25, 2024

We will indeed rebuild the connector if the stream reader in source executor throws an error. But before #14611, we didn't stop the cdc engine when it runs into trouble. So that the channel between executor and jvm still alive, and no errors will be seen.
After we fix the problem, we will rebuild a connector when it exits.

@StrikeW StrikeW closed this as completed Jan 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@StrikeW StrikeW

Labels
type/feature
Projects
None yet
Milestone
release-1.7
Development

No branches or pull requests
1 participant
@StrikeW