Skip to content

Commit f0d3f08

Browse files
committed
rename dir and update troubleshooting doc
Signed-off-by: chenqiming <[email protected]>
1 parent cb6bf2b commit f0d3f08

39 files changed

+60
-0
lines changed
File renamed without changes.

docs/troubleshooting-and-faq/troubleshooting.md

+60
Original file line numberDiff line numberDiff line change
@@ -76,3 +76,63 @@ JindoFS:
7676
> As you can see from above command and help message, option `--name` and `--namespace` specified the name and namespace of Alluxio Runtime respectively.
7777
7878
All the logs will be packed in a package under execution path.
79+
80+
## Debug Fuse Pod
81+
82+
If the application Pod is in the `ContainerCreating` or `Pending` state for a long time and cannot be created due to the CSI Plugin issue, it is usually caused by the state of the Fuse Pod in the same node is not correct. You can follow these steps to troubleshoot.
83+
84+
### Check Application Pods Events
85+
86+
The first step in debugging Fuse is to check the application Pod information. Use the following command to check the current status and recent events of the Pod.
87+
88+
```shell
89+
kubectl describe pods ${POD_NAME}
90+
```
91+
92+
Similar to the following information, but may not be identical, but all point to the reason for FailedMount.
93+
94+
```shell
95+
kubectl describe po nginx-0
96+
...
97+
Events:
98+
Type Reason Age From Message
99+
---- ------ ---- ---- -------
100+
Normal Scheduled 30s default-scheduler Successfully assigned default/nginx-0 to testnode
101+
Warning FailedMount 1s kubelet MountVolume.MountDevice failed for volume "default-shared-data" : rpc error: code = Unknown desc = fuse pod on node testnode is not ready
102+
```
103+
104+
### Get the information of the Fuse Pod corresponding to this application Pod
105+
106+
At this point you need to check the status of the Fuse Pod of this node, first use the following command to get the information of the node where the current application Pod is located, the output corresponding to the NODE column is the node where the application Pod is located.
107+
108+
109+
```shell
110+
kubectl get pods ${POD_NAME} -owide
111+
```
112+
113+
For example, the following node where Fuse Pod is located is testnode:
114+
115+
```shell
116+
kubectl get pods nginx-0 -owide
117+
NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
118+
nginx-0 0/1 ContainerCreating 0 17m <none> testnode <none> <none>
119+
```
120+
121+
122+
Get this Fuse Pod's detail information:
123+
124+
```shell
125+
kubectl get po -owide | grep ${NODE_NAME} | grep -i fuse
126+
```
127+
128+
129+
In the following example, the Fuse Pod is `shared-data-alluxio-fuse-w6lcp`, and you can see that the Pod is in a failed state:
130+
131+
```shell
132+
kubectl get po -owide | grep testnode | grep fuse
133+
shared-data-alluxio-fuse-w6lcp 0/1 CrashLoopBackOff 10 29m 192.168.0.233 testnode <none> <none>
134+
```
135+
136+
### Troubleshoot the Fuse Pod
137+
138+
You can follow the [Kubernetes documentation](https://kubernetes.io/docs/tasks/debug/debug-application/debug-running-pod/) to troubleshoot the issue with this Fuse Pod.
File renamed without changes.

0 commit comments

Comments
 (0)