Skip to content
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

session: fix unseccessfully isolation read engines init session (#16465) #16482

Merged
merged 8 commits into from
Apr 26, 2020

Conversation

sre-bot
Copy link
Contributor

@sre-bot sre-bot commented Apr 16, 2020

cherry-pick #16465 to release-3.1


What problem does this PR solve?

Problem Summary: as the title says.

What is changed and how it works?

What's Changed: isolation read engines should be re-init after config load.

Related changes

  • Need to cherry-pick to the release branch

Check List

Tests

  • Unit test
  • Integration test

Side effects

  • Performance regression
    • Consumes more CPU

Signed-off-by: sre-bot <sre-bot@pingcap.com>
@sre-bot
Copy link
Contributor Author

sre-bot commented Apr 16, 2020

/run-all-tests

Copy link
Contributor

@SunRunAway SunRunAway left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@lzmhhh123 Please resolve the conflicting files.

Copy link
Member

@zz-jason zz-jason left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@lzmhhh123 please fix CI:

[2020-04-17T08:20:29.741Z] main_test.go:43:

[2020-04-17T08:20:29.741Z]     c.Assert(variable.SysVars[variable.TiDBIsolationReadEngines].Value, Equals, "tikv, tiflash, tidb")

[2020-04-17T08:20:29.741Z] ... obtained string = "tikv, tiflash"

[2020-04-17T08:20:29.741Z] ... expected string = "tikv, tiflash, tidb"

@zz-jason zz-jason removed the request for review from crazycs520 April 22, 2020 12:43
@zz-jason zz-jason added the priority/release-blocker This issue blocks a release. Please solve it ASAP. label Apr 26, 2020
@zz-jason
Copy link
Member

/run-all-tests

@lzmhhh123 lzmhhh123 force-pushed the release-3.1-39cc8935cdc9 branch from 3261848 to 0f03107 Compare April 26, 2020 05:35
@lzmhhh123
Copy link
Contributor

/run-all-tests

@lzmhhh123
Copy link
Contributor

/run-all-tests

Copy link
Member

@zz-jason zz-jason left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@zz-jason zz-jason requested a review from SunRunAway April 26, 2020 06:49
@zz-jason zz-jason added the status/LGT1 Indicates that a PR has LGTM 1. label Apr 26, 2020
Copy link
Contributor

@SunRunAway SunRunAway left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@SunRunAway SunRunAway removed the status/LGT1 Indicates that a PR has LGTM 1. label Apr 26, 2020
@SunRunAway SunRunAway added status/can-merge Indicates a PR has been approved by a committer. status/LGT2 Indicates that a PR has LGTM 2. labels Apr 26, 2020
@sre-bot
Copy link
Contributor Author

sre-bot commented Apr 26, 2020

/run-all-tests

@sre-bot
Copy link
Contributor Author

sre-bot commented Apr 26, 2020

/run-all-tests

@sre-bot sre-bot merged commit 6f49324 into pingcap:release-3.1 Apr 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/session priority/release-blocker This issue blocks a release. Please solve it ASAP. status/can-merge Indicates a PR has been approved by a committer. status/LGT2 Indicates that a PR has LGTM 2. type/bugfix This PR fixes a bug. type/3.1-cherry-pick
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants