Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.
Original topic: PD调度Region的问题
[TiDB Usage Environment] Production Environment / Testing / PoC
[TiDB Version] v6.1.0
[Reproduction Path] What operations were performed when the issue occurred
[Encountered Issue: Issue Phenomenon and Impact]
The issue is as follows:
I noticed a problem in the documentation. Are the isolation-level parameter and the location-labels parameter of PD conflicting?
If deployed in a multi-data center environment, by setting a reasonable scheduling strategy, such as the one below, can we achieve high availability and balanced scheduling of Region Leaders? In this case, what is the significance of the isolation-level parameter?
location-labels = ["zone", "rack", "host"]
[Resource Configuration]
[Attachments: Screenshots/Logs/Monitoring]
location-labels: Set the hierarchical information of the labels.
isolation-level: Set the isolation level on the label hierarchy, such as rack. When the number of different racks meets the replica count requirement, it ensures that the same rack does not have the same replica of TiKV.
Assuming there are 2 zones and the isolation level is set to rack, does this mean that the data replicas are distributed across multiple racks within the same zone to enhance isolation? If a rack fails, the damage is minimized? Can it be understood this way?
Yes, the main goal is to prevent multiple machine failures from causing multiple replica failures. The specific level to which it can be set depends on the resources and requirements.
If you only set location-labels = [“zone”, “rack”, “host”], it should also work in single-zone and multi-zone environments, right? Regions should also be balanced and scheduled for high availability, right?
Additionally, I feel that if it’s not a large TiDB cluster architecture or a cross-data center cluster architecture, it might not be necessary to set the isolation-level parameter.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
|
username: 孤君888
|
username: 
|
username: