Support for lock and unlock tables #7139
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Signed-off-by: Harshit Gangal harshit@planetscale.com
Backport
NO
Status
READY
Description
Currently we allow lock tables and unlock tables to be passed down to vttablet. This does not work as expected because the lock is taken on any connection from the pool and next query is executed on second random connection from the pool.
This causes the mysql to be locked for all the connections.
Current PR will not allow these statements to be sent down the vttablet and will log a warning message.
Related Issue(s)
Fixes #7070
Impacted Areas in Vitess
List general components of the application that this PR will affect: