This is an automated email from the ASF dual-hosted git repository.

zhuqi pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/yunikorn-site.git


The following commit(s) were added to refs/heads/master by this push:
     new 2d27a4839e [YUNIKORN-2812] Add troubleshooting docs for bind pod 
volumes timeout (#462)
2d27a4839e is described below

commit 2d27a4839ef16a034eef5349010d19a92671430c
Author: qzhu <[email protected]>
AuthorDate: Mon Aug 19 11:04:59 2024 +0800

    [YUNIKORN-2812] Add troubleshooting docs for bind pod volumes timeout (#462)
    
    Closes: #462
    
    Signed-off-by: qzhu <[email protected]>
---
 docs/user_guide/troubleshooting.md | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/docs/user_guide/troubleshooting.md 
b/docs/user_guide/troubleshooting.md
index 05b5237dc2..cf4f71dd48 100644
--- a/docs/user_guide/troubleshooting.md
+++ b/docs/user_guide/troubleshooting.md
@@ -217,6 +217,13 @@ the garbage collection is not working properly.
 
 *Solution*: check the placeholder `ownerReference` and the garbage collector 
in Kubernetes.    
 
+# Task failed with pod volume binding time out
+*Reason*: The timeout value for service.volumeBindTimeout (which is set at 10 
seconds by default). 
+But some cases, the pod volume binding will take more time, for example:
+When a node brought in by the autoscaler where the csi-node daemonset hasn’t 
been installed yet, which causes a delay with the volume binding (15-20 
seconds). 
+
+
+*Solution*: Increase the timeout value for service.volumeBindTimeout, for 
example, set it to 60 seconds.
 
 ## Still got questions?
 


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to