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

Isolation read don't take effort after reboot tidb-server #17257

Closed
lzmhhh123 opened this issue May 18, 2020 · 0 comments · Fixed by #17258
Closed

Isolation read don't take effort after reboot tidb-server #17257

lzmhhh123 opened this issue May 18, 2020 · 0 comments · Fixed by #17258
Assignees
Labels
severity/major sig/planner SIG: Planner type/bug The issue is confirmed as a bug.
Milestone

Comments

@lzmhhh123
Copy link
Contributor

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

Set the value of tidb-isolation-read-engines as ["tikv"] in tidb toml, but the sql plab choose the tiflash.

image

image

2. What did you expect to see? (Required)

The sql plan for isolation read tikv is tikv.

3. Affected version (Required)

mysql> select tidb_version()\G
*************************** 1. row ***************************
tidb_version(): Release Version: v4.0.0-rc-141-g7267747ae
Git Commit Hash: 7267747
Git Branch: jira-4.0
UTC Build Time: 2020-04-28 08:28:57
GoVersion: go1.13
Race Enabled: false
TiKV Min Version: v3.0.0-60965b006877ca7234adaced7890d7b029ed1306
Check Table Before Drop: false
1 row in set (0.00 sec)

4. Root Cause Analysis

SysVars and session.variables aren't consistent in isolation-read-engines.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
severity/major sig/planner SIG: Planner type/bug The issue is confirmed as a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants