github
/
k3s
mirror of https://github.com/k3s-io/k3s
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Merge pull request #27491 from yujuhong/shorter_timeout 

Set the podAttachAndMountTimeout to a lower value
pull/6/head
Saad Ali 2016-06-15 22:57:33 -07:00 committed by GitHub
parent 523e83fbb0 9bc2b43064
commit 23f9d9f4cf
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 desiredStateOfWorldPopulatorLoopSleepPeriod time.Duration = 100 * time.Millisecond
// podAttachAndMountTimeout is the maximum amount of time the // podAttachAndMountTimeout is the maximum amount of time the
// GetVolumesForPod call will wait for all volumes in the specified pod to // WaitForAttachAndMount call will wait for all volumes in the specified pod
// be attached and mounted. Set to 20 minutes because we've seen cloud // to be attached and mounted. Even though cloud operations can take several
// operations take several minutes to complete for some volume plugins in // minutes to complete, we set the timeout to 2 minutes because kubelet
// some cases. While the GetVolumesForPod method is waiting it only blocks // will retry in the next sync iteration. This frees the associated
// other operations on the same pod, other pods are not affected. // goroutine of the pod to process newer updates if needed (e.g., a delete
podAttachAndMountTimeout time.Duration = 20 * time.Minute // request to the pod).
podAttachAndMountTimeout time.Duration = 2 * time.Minute
// podAttachAndMountRetryInterval is the amount of time the GetVolumesForPod // podAttachAndMountRetryInterval is the amount of time the GetVolumesForPod
// call waits before retrying // call waits before retrying