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.

Sign up for GitHub

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

Jump to bottom

Update configure-placement-rules.md #11019

Merged
merged 2 commits into from Oct 26, 2022
Merged

Update configure-placement-rules.md #11019

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
5a67725
Update configure-placement-rules.md
qiancai Oct 26, 2022
9aaec40
Update configure-placement-rules.md
qiancai Oct 26, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
4 changes: 2 additions & 2 deletions configure-placement-rules.md
View file
Open in desktop
Expand Up @@ -432,7 +432,7 @@ Add a separate rule for the row key of the table and limit `count` to `2`. Use `

### Scenario 4: Add two follower replicas for a table in the Beijing node with high-performance disks

The following example shows a more complicated `label_constraints` configuration. In this rule, the replicas must be placed in the `bj1` or `bj2` machine room, and the disk type must not be `ssd`.
The following example shows a more complicated `label_constraints` configuration. In this rule, the replicas must be placed in the `bj1` or `bj2` machine room, and the disk type must be `nvme`.

{{< copyable "" >}}

Expand All @@ -446,7 +446,7 @@ The following example shows a more complicated `label_constraints` configuration
"count": 2,
"label_constraints": [
{"key": "zone", "op": "in", "values": ["bj1", "bj2"]},
{"key": "disk", "op": "notIn", "values": ["ssd"]}
{"key": "disk", "op": "in", "values": ["nvme"]}
],
"location_labels": ["host"]
}
Expand Down