-
Notifications
You must be signed in to change notification settings - Fork 997
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
Support min_gtid annotation #2469
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@kirs according to the logic the min_gtid takes precedence over gtid_from_hostgroup which is configured in query rules. It looks like correct behavior.
There several issues that should be resolved before merge.
Thanks for review @Val214! I pushed another commit that adds GTID validation, to make sure that we only set |
Automated message: PR pending admin approval for build testing |
@kirs, thank you for your changes but there is an issue that still should be resolved. The |
I somehow assumed that I pushed a commit that makes Thanks again for reviewing this. |
in handler___client_DSS_QUERY_SENT___server_DSS_NOT_INITIALIZED__get_connection
LGTM! |
This PR is an attempt to get #2444 done. I'm probably missing a lot, and this is the first time I do C++, so I'd really appreciate the feedback.
How does it work?
session_track_gtids
): in a cookie/session for web requests, and in Redis for batch jobs.min_gtid
is passed in a comment to ProxySQL, which lets it choose any read replica that satisfies that GTID.#2444 (comment) has a diagram showing how that can be leveraged by a typical web app.
Questions:
I'm looking forward to your feedback ❤️