github/kubernetes
1
0
Fork 0
mirror of https://github.com/k3s-io/kubernetes.git synced 2025-07-21 10:51:29 +00:00
Code Issues Projects Releases Wiki Activity

Set the podAttachAndMountTimeout to a lower value

Browse Source 
If the mount operation exceeds the timeout, it will return an error and the
pod worker will retry in the next sync (10s or less). Compared with the
original value (i.e., 10 minutes), this frees the pod worker sooner to process
pod updates, if there are any.
This commit is contained in:
Yu-Ju Hong 2016-06-15 16:01:15 -07:00
parent 38cd0d078e
commit 9bc2b43064
1 changed files with 7 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
pkg/kubelet/volume/volume_manager.go
View File

@ -49,12 +49,13 @@ const (
desiredStateOfWorldPopulatorLoopSleepPeriod time.Duration = 100 * time.Millisecond
// podAttachAndMountTimeout is the maximum amount of time the
// GetVolumesForPod call will wait for all volumes in the specified pod to
// be attached and mounted. Set to 20 minutes because we've seen cloud
// operations take several minutes to complete for some volume plugins in
// some cases. While the GetVolumesForPod method is waiting it only blocks
// other operations on the same pod, other pods are not affected.
podAttachAndMountTimeout time.Duration = 20 * time.Minute
// WaitForAttachAndMount call will wait for all volumes in the specified pod
// to be attached and mounted. Even though cloud operations can take several
// minutes to complete, we set the timeout to 2 minutes because kubelet
// will retry in the next sync iteration. This frees the associated
// goroutine of the pod to process newer updates if needed (e.g., a delete
// request to the pod).
podAttachAndMountTimeout time.Duration = 2 * time.Minute
// podAttachAndMountRetryInterval is the amount of time the GetVolumesForPod
// call waits before retrying