Setting the engine for one TiDB server will affect all TiDB servers; individual instances cannot be configured separately

Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: 7.4 设置某个tidbserver的引擎后所有tidbserver都会生效,不能单独设置某个实例的

| username: Running

Two tidbserver instances, one set as tikv, tidb and the other set as tidb, tiflash. As a result, both instances are tidb, tikv, and the individual settings for a specific instance do not take effect; the same operation works on version 7.0.

| username: Running | Original post link

Reproduction method: Initialize two TiDB server nodes, one TiKV, and one TiFlash.

| username: Billmay表妹 | Original post link

Please follow the bug report template

Didn’t understand the question
Bug Report
Clearly and accurately describe the issue you found. Providing any steps to reproduce the issue can help the development team address it promptly.
[TiDB Version]
[Impact of the Bug]

[Possible Steps to Reproduce the Issue]

[Observed Unexpected Behavior]

[Expected Behavior]

[Related Components and Specific Versions]

[Other Background Information or Screenshots]
Such as cluster topology, system and kernel versions, application app information, etc. If the issue is related to SQL, please provide the SQL statements and related table schema information. If there are critical errors in the node logs, please provide the relevant node log content or files. If some business-sensitive information is inconvenient to provide, please leave your contact information, and we will communicate with you privately.

| username: xfworld | Original post link

Are you going to set hit or choose an engine?

| username: Running | Original post link

Directly set the engine of a specific tidbserver instance to the TiFlash engine.

| username: xfworld | Original post link

There is no such feature.

| username: Kongdom | Original post link

You’re referring to this, right?

| username: tidb菜鸟一只 | Original post link

Do you mean setting the session-level tidb_isolation_read_engines variable, but all the TiDB servers changed?
I tested it and couldn’t reproduce the issue.


| username: Kongdom | Original post link

The original post also verified that there seems to be a conflict between the configuration file and system variables~

| username: tidb菜鸟一只 | Original post link

So, is it a conflict between the configuration file and the system variables?

| username: Kongdom | Original post link

Feedback has been given to the product and research team, let’s wait for the conclusion. :yum:

| username: Running | Original post link

Is there any progress on this?

| username: Billmay表妹 | Original post link

Keep an eye on the thread replies~

| username: Billmay表妹 | Original post link

set `isolation-read` for each tidb instance can't work · Issue #48177 · pingcap/tidb · GitHub is a bug, an issue has been opened.

| username: system | Original post link

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.