Skip to content

[15.0] Fix query list override issue on mysql restart (#11309)#11506

Merged
harshit-gangal merged 2 commits intovitessio:release-15.0from
planetscale:15-cp-11309
Oct 15, 2022
Merged

[15.0] Fix query list override issue on mysql restart (#11309)#11506
harshit-gangal merged 2 commits intovitessio:release-15.0from
planetscale:15-cp-11309

Conversation

@harshit-gangal
Copy link
Member

Cherry pick of #11309

* test: added failing e2e test

Signed-off-by: Harshit Gangal <harshit@planetscale.com>

* log txID and reserveID in stream execute

Signed-off-by: Harshit Gangal <harshit@planetscale.com>

* fix: maintain list of qd per key on the map and check for current connection id while removing

Signed-off-by: Harshit Gangal <harshit@planetscale.com>

* added additional comments

Signed-off-by: Harshit Gangal <harshit@planetscale.com>

Signed-off-by: Harshit Gangal <harshit@planetscale.com>
@vitess-bot
Copy link
Contributor

vitess-bot bot commented Oct 14, 2022

Review Checklist

Hello reviewers! 👋 Please follow this checklist when reviewing this Pull Request.

General

  • Ensure that the Pull Request has a descriptive title.
  • If this is a change that users need to know about, please apply the release notes (needs details) label so that merging is blocked unless the summary release notes document is included.

If a new flag is being introduced:

  • Is it really necessary to add this flag?
  • Flag names should be clear and intuitive (as far as possible)
  • Help text should be descriptive.
  • Flag names should use dashes (-) as word separators rather than underscores (_).

If a workflow is added or modified:

  • Each item in Jobs should be named in order to mark it as required.
  • If the workflow should be required, the maintainer team should be notified.

Bug fixes

  • There should be at least one unit or end-to-end test.
  • The Pull Request description should include a link to an issue that describes the bug.

Non-trivial changes

  • There should be some code comments as to why things are implemented the way they are.

New/Existing features

  • Should be documented, either by modifying the existing documentation or creating new documentation.
  • New features should have a link to a feature request issue or an RFC that documents the use cases, corner cases and test cases.

Backward compatibility

  • Protobuf changes should be wire-compatible.
  • Changes to _vt tables and RPCs need to be backward compatible.
  • vtctl command output order should be stable and awk-able.
  • RPC changes should be compatible with vitess-operator
  • If a flag is removed, then it should also be removed from VTop, if used there.

@harshit-gangal harshit-gangal added this to the v15.0 milestone Oct 14, 2022
Signed-off-by: Harshit Gangal <harshit@planetscale.com>
@harshit-gangal harshit-gangal merged commit 1047f7e into vitessio:release-15.0 Oct 15, 2022
@harshit-gangal harshit-gangal deleted the 15-cp-11309 branch October 15, 2022 16:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants