Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow reflector to do full resync periodically #4923

Merged
merged 2 commits into from
Mar 4, 2015

Conversation

lavalamp
Copy link
Member

Part 1 of several for #4877.

This PR doesn't change any behavior; the new functionality is off everywhere.

This is necessary, but not yet sufficient, to refactor our current replication controller to be more like our scheduler.

@pmorie
Copy link
Member

pmorie commented Feb 28, 2015

@ironcladlou @derekwaynecarr @bparees
On Fri, Feb 27, 2015 at 8:04 PM Daniel Smith notifications@github.com
wrote:

Part 1 of several for #4877
#4877.

This PR doesn't change any behavior; the new functionality is off
everywhere.

This is necessary, but not yet sufficient, to refactor our current

replication controller to be more like our scheduler.

You can view, comment on, or merge this pull request online at:

#4923
Commit Summary

  • clean up poller test to not make infinite log messages
  • add occasional polling to reflector

File Changes

Patch Links:


Reply to this email directly or view it on GitHub
#4923.

@ironcladlou
Copy link
Contributor

I like where this is going. Taking the conversation about delete handling over to #4877 for now.

@derekwaynecarr
Copy link
Member

This PR is LGTM.

Per our discussion, will you look to make reflector.resourceVersion somehow available to the cache.Store so I can do the pattern of asking a store if its state has changed since I last viewed it?

derekwaynecarr added a commit that referenced this pull request Mar 4, 2015
Allow reflector to do full resync periodically
@derekwaynecarr derekwaynecarr merged commit cb1e044 into kubernetes:master Mar 4, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants