Skip to content

Commit 7d457d5

Browse files
committed
fix format
1 parent 55e0bd6 commit 7d457d5

File tree

2 files changed

+8
-8
lines changed

2 files changed

+8
-8
lines changed

en/deploy-failures.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -51,9 +51,9 @@ If the `StorageClass` of the PVC cannot be found, take the following steps:
5151

5252
3. Update the configuration file:
5353

54-
* If you want to run a backup/restore task, first execute `kubectl delete bk ${backup_name} -n ${namespace}` to delete the old backup/restore task, and then execute `kubectl apply -f backup.yaml` to create a new backup/restore task.
54+
If you want to run a backup/restore task, first execute `kubectl delete bk ${backup_name} -n ${namespace}` to delete the old backup/restore task, and then execute `kubectl apply -f backup.yaml` to create a new backup/restore task.
5555

56-
4. Delete the corresponding PVCs.
56+
4. Delete the corresponding PVCs:
5757

5858
```shell
5959
kubectl delete pvc -n ${namespace} ${pvc_name}

zh/deploy-failures.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ Pod 处于 Pending 状态,通常都是资源不满足导致的,比如:
2929

3030
此时,可以通过 `kubectl describe pod` 命令查看 Pending 的具体原因:
3131

32-
```
32+
```shell
3333
kubectl describe po -n ${namespace} ${pod_name}
3434
```
3535

@@ -43,19 +43,19 @@ kubectl describe po -n ${namespace} ${pod_name}
4343

4444
1. 通过以下命令获取集群中可用的 StorageClass:
4545

46-
```
46+
```shell
4747
kubectl get storageclass
4848
```
4949

5050
2. 将 `storageClassName` 修改为集群中可用的 StorageClass 名字。
5151

5252
3. 使用下述方式更新配置文件:
5353

54-
* 如果是运行 backup/restore 的备份/恢复任务,首先需要运行 `kubectl delete bk ${backup_name} -n ${namespace}` 删掉老的备份/恢复任务,再运行 `kubectl apply -f backup.yaml` 重新创建新的备份/恢复任务。
54+
如果是运行 backup/restore 的备份/恢复任务,首先需要运行 `kubectl delete bk ${backup_name} -n ${namespace}` 删掉老的备份/恢复任务,再运行 `kubectl apply -f backup.yaml` 重新创建新的备份/恢复任务。
5555

56-
4. 将对应的 PVC 也都删除。
56+
4. 删除对应的 PVC
5757

58-
```
58+
```shell
5959
kubectl delete pvc -n ${namespace} ${pvc_name}
6060
```
6161

@@ -79,7 +79,7 @@ kubectl -n ${namespace} logs -f ${pod_name}
7979
kubectl -n ${namespace} logs -p ${pod_name}
8080
```
8181

82-
确认日志中的错误信息后,可以根据 [tidb-server 启动报错](https://docs.pingcap.com/zh/tidb/stable/troubleshoot-tidb-cluster#tidb-server-%E5%90%AF%E5%8A%A8%E6%8A%A5%E9%94%99)[tikv-server 启动报错](https://docs.pingcap.com/zh/tidb/stable/troubleshoot-tidb-cluster#tikv-server-%E5%90%AF%E5%8A%A8%E6%8A%A5%E9%94%99)[pd-server 启动报错](https://docs.pingcap.com/zh/tidb/stable/troubleshoot-tidb-cluster#pd-server-%E5%90%AF%E5%8A%A8%E6%8A%A5%E9%94%99)中的指引信息进行进一步排查解决。
82+
确认日志中的错误信息后,可以根据 [tidb-server 启动报错](https://docs.pingcap.com/zh/tidb/stable/troubleshoot-tidb-cluster/#tidb-server-启动报错 )、[tikv-server 启动报错](https://docs.pingcap.com/zh/tidb/stable/troubleshoot-tidb-cluster/#tikv-server-启动报错)、[pd-server 启动报错](https://docs.pingcap.com/zh/tidb/stable/troubleshoot-tidb-cluster/#pd-server-启动报错)中的指引信息进行进一步排查解决。
8383

8484
### ulimit 不足
8585

0 commit comments

Comments
 (0)