-
Notifications
You must be signed in to change notification settings - Fork 25
[QUESTION] Mitigation around AWS RDS write forwarding in read only replicas #293
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
Comments
Thanks for providing the details that really helps. Let me check if we can implement this without affecting current behavior. |
I have a support call with AWS, they can't reproduce, before changing anything let me come back to you with the results of that call. |
Got it :D |
Sorry for the late reply. I guess to make this work with AWD RDS and write forwarding you must not not issue |
Thanks for update :D |
Hi, @ls-urs-keller . ![]() ![]() ![]() Since the queries in the reproducible repository do not include Thank you! |
Summary
We had some issues around AWS RDS with cross region replication and rw/ro replicas with write forwarding.
I believe it is a bug on the AWS side. But it would be good if it could be mitigated.
Analysis here: https://github.com/ls-urs-keller/r2dbc-test
Mitigation: don't issue "START TRANSACTION READ WRITE" but either just "BEGIN" or "START TRANSACTION" if the transaction is readonly=false.
Checklist
The text was updated successfully, but these errors were encountered: