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

[Improvement][AMS]: Improve the high concurrency processing capability of the allocateTransactionId interface #393

Closed
3 tasks done
hameizi opened this issue Sep 21, 2022 · 0 comments · Fixed by #424
Closed
3 tasks done

Comments

@hameizi
Copy link
Contributor

hameizi commented Sep 21, 2022

Search before asking

  • I have searched in the issues and found no similar issues.

What would you like to be improved?

When multiple tasks(like upsert partial fields of arctic table with Flink) write data to the same table, apply for TransActionID at the same time. So we should improve the high concurrency processing capability of the allocateTransactionId interface.

How should we improve?

we can compare the old and new transactionid when update row in mysql, like update table_metadata where tablename={} and current_tx_id={old_tx_id}. And we get the update return value(Number of rows affected), if the value greater than 0 means update success else retry more(just like cas).

Are you willing to submit PR?

  • Yes I am willing to submit a PR!

Code of Conduct

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