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.

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

Feature request: support passing down Debezium properties #14464

Closed
sheltonsuen opened this issue Jan 9, 2024 · 2 comments
Closed

Feature request: support passing down Debezium properties #14464

sheltonsuen opened this issue Jan 9, 2024 · 2 comments

Comments

@sheltonsuen
Copy link

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

Yes, when using MySQL CDC we may need custom some properties of Debezium,
The default behavior of Risingwave MySQL CDC will create lock on the MySQL instance and cause other service unaviliable long time during snapshot sync time,

Describe the solution you'd like

we can custom the snapshot.locking.mode of Debezium

Describe alternatives you've considered

No response

Additional context

No response

@github-actions github-actions bot added this to the release-1.7 milestone Jan 9, 2024
@xxchan
Copy link
Member

xxchan commented Jan 9, 2024

We've supported lock-free MySQL CDC in v1.5.0. What's the RisingWave version are you using?

Besides, RisingWave's MySQL CDC has a customized lock-free algorithm instead of solely relying on Debezium, so we can't use snapshot.locking.mode for that.

@sheltonsuen
Copy link
Author

Version: 1.5.4

we didn't save any logs for that, but we do have noticed the MySQL CDC user has a long transaction lock,

I will retry later to see if there still this problem

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants