Skip to content

Commit 19ea4e4

Browse files
committed
Polish the doc
Signed-off-by: JaySon-Huang <[email protected]>
1 parent 7648d82 commit 19ea4e4

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

tiflash/troubleshoot-tiflash.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -153,7 +153,7 @@ If TiFlash replicas consistently fail to be created since the TiDB cluster is de
153153
- If `true` is returned, go to the next step.
154154
- If `false` is returned, [enable the Placement Rules feature](/configure-placement-rules.md#enable-placement-rules) and go to the next step.
155155
156-
2. Check whether the TiFlash process is working correctly by viewing `UpTime` on the TiFlash-Summary monitoring panel.
156+
2. Check whether the TiFlash process is working normally by the `UpTime` on the TiFlash-Summary monitoring panel.
157157
158158
3. Check whether the connection between TiFlash and PD is normal through `pd-ctl`.
159159
@@ -170,7 +170,7 @@ If TiFlash replicas consistently fail to be created since the TiDB cluster is de
170170
```
171171
172172
- If the value of `count` does not exceed the number of TiKV nodes in the cluster, go to the next step.
173-
- If the value of `count` is greater than the number of TiKV nodes in the cluster, the PD does not replicate data to the TiFlash node. To address this issue, change `count` to an integer fewer than or equal to the number of TiKV nodes in the cluster.
173+
- If the value of `count` is greater than the number of TiKV nodes in the cluster. For example, if there are only 1 TiKV nodes in a testing cluster while the count is 3, then PD will not add any Region peer to the TiFlash node. To address this issue, change `count` to an integer fewer than or equal to the number of TiKV nodes in the cluster.
174174
175175
> **Note:**
176176
>

0 commit comments

Comments
 (0)