Change:
Consider reducing the PVClaimBinderSyncPeriod from 10 minutes down to something more reasonable, so that volumes don't sit around unbound for half an hour if it fails twice. This would reduce the impact of issues like until the binder/recycler/provosioner consolidation/refactor is complete. CC
+100
do you remember what was the reason for 10 minutes?
I checked provisioner and recycler, lowering the sync period should not harm them. Still, it will impact deleter a bit. Now we try to delete a volume three times every sync-period (10 minutes), mostly because if user deletes a pod that uses a volume and deletes also the PVC bound to it, the volume is still attached to the node for some time and all deletion attempts fail. I've seen AWS detach taking around 5 minutes in some cases. So, if we lower the timer, we should also increase the number of retries. Or have a different retry timer for deletion.

Discussion:
NodeSyncPeriod:                    unversioned.Duration{Duration: 10 * time.Second}, ResourceQuotaSyncPeriod:           unversioned.Duration{Duration: 5 * time.Minute}, NamespaceSyncPeriod:               unversioned.Duration{Duration: 5 * time.Minute}, <del> PVClaimBinderSyncPeriod:           unversioned.Duration{Duration: 10 * time.Minute}, </del> <ins> PVClaimBinderSyncPeriod:           unversioned.Duration{Duration: 15 * time.Second}, </ins> HorizontalPodAutoscalerSyncPeriod: unversioned.Duration{Duration: 30 * time.Second}, DeploymentControllerSyncPeriod:    unversioned.Duration{Duration: 30 * time.Second}, MinResyncPeriod:                   unversioned.Duration{Duration: 12 * time.Hour},

--pv-recycler-pod-template-filepath-hostpath="": The file path to a pod definition used as a template for HostPath persistent volume recycling. This is for development and testing only and will not work in a multi-node cluster. --pv-recycler-pod-template-filepath-nfs="": The file path to a pod definition used as a template for NFS persistent volume recycling --pv-recycler-timeout-increment-hostpath=30: the increment of time added per Gi to ActiveDeadlineSeconds for a HostPath scrubber pod.  This is for development and testing only and will not work in a multi-node cluster. <del> --pvclaimbinder-sync-period=10m0s: The period for syncing persistent volumes and persistent volume claims </del> <ins> --pvclaimbinder-sync-period=15s: The period for syncing persistent volumes and persistent volume claims </ins> --replicaset-lookup-cache-size=4096: The the size of lookup cache for replicatsets. Larger number = more responsive replica management, but more MEM load. --replication-controller-lookup-cache-size=4096: The the size of lookup cache for replication controllers. Larger number = more responsive replica management, but more MEM load. --resource-quota-sync-period=5m0s: The period for syncing quota usage status in the system

--terminated-pod-gc-threshold=12500: Number of terminated pods that can exist before the terminated pod garbage collector starts deleting terminated pods. If <= 0, the terminated pod garbage collector is disabled. ``` <del> ###### Auto generated by spf13/cobra on 26-May-2016 </del> <ins> ###### Auto generated by spf13/cobra on 27-May-2016 </ins> <!-- BEGIN MUNGE: GENERATED_ANALYTICS -->

func NewPersistentVolumeControllerOptions() PersistentVolumeControllerOptions { return PersistentVolumeControllerOptions{ <del> PVClaimBinderSyncPeriod: 10 * time.Minute, </del> <ins> PVClaimBinderSyncPeriod: 15 * time.Second, </ins> VolumeConfigFlags: VolumeConfigFlags{ // default values here PersistentVolumeRecyclerMaximumRetry:             3,