-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Does context cancellation cancel the underlying query? #731
Comments
Hi, I'm the author of #608.
Yes, my implement doesn't kill the query running on the server. Line 270 in 9181e3a
|
FYI, you can limit query execution time via hint. |
@shogo82148 @methane Thanks. |
Are there any plans on fixing that TODO? |
Looks like it is in a milestone btw. For others adding circuit breaking to services and find that queries persist in mysql, you may want to watch and react to these issues so the maintainers know there is interest. Most of my peers expected this to work because they were more familiar with postgres where such workflows are known to work, are more easy to implement / are supported by the query session natively without making more connections. For now I am documenting in my org that mysql is less friendly here and effective support for such a feature would warrant mysql server changing their connection interface. A work around would be nice since we have so much using mysql at the moment. :-) |
After reading #496 and #608, I was under the impression that in the above example, the underlying query would get canceled mid-execution, but that doesn't seem to be the case. It still takes 10 seconds to return (and the query shows in MySQL process list), albeit with the error
sql: Rows are closed
. Does this mean that the driver isn't actually able to cancel the underlying query running on the server?The text was updated successfully, but these errors were encountered: