From 8454aaf1be5f783e75a58f36a89f1cfa5e715ac3 Mon Sep 17 00:00:00 2001 From: Mike Spreitzer Date: Mon, 6 Jan 2020 01:56:52 -0500 Subject: [PATCH] Noted divergence between requestedResyncPeriod and resyncPeriod Kubernetes-commit: eef49c965f471d575aef8de5f071ffc6fd31c44d --- tools/cache/shared_informer.go | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/tools/cache/shared_informer.go b/tools/cache/shared_informer.go index 59c13fe7..13ef390f 100644 --- a/tools/cache/shared_informer.go +++ b/tools/cache/shared_informer.go @@ -611,11 +611,12 @@ type processorListener struct { // `resyncCheckPeriod`. requestedResyncPeriod time.Duration // resyncPeriod is the threshold that will be used in the logic - // for this listener. This value does not differ from - // requestedResyncPeriod. The actual time between resyncs depends - // on when the sharedProcessor's `shouldResync` function is - // invoked and when the sharedIndexInformer processes `Sync` type - // Delta objects. + // for this listener. This value differs from + // requestedResyncPeriod only when the sharedIndexInformer does + // not do resyncs, in which case the value here is zero. The + // actual time between resyncs depends on when the + // sharedProcessor's `shouldResync` function is invoked and when + // the sharedIndexInformer processes `Sync` type Delta objects. resyncPeriod time.Duration // nextResync is the earliest time the listener should get a full resync nextResync time.Time