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

Introduce cached client behind feature flag #1037

Merged
merged 3 commits into from Jun 3, 2021

Commits on Jun 3, 2021

  1. Add back components of remote watch needed for cached client

    Save client
    
    It is alive
    
    Checkpoint
    
    Pre cleanup
    
    Log name of migcluster starting remote watch for
    
    Filter list of events with exact watch to allow for cache usage
    
    Start transitioning event logging to keying on UID
    
    clientMap access safety
    
    add timout on spinlock
    
    add consistency check for remote watch
    
    add all clients to the shared client map to avoid reconstruction
    
    change spin lock implementation
    
    improve cache consistency logic for clients
    
    Rename vars related to cached client
    
    Pre-refactor to separate client names
    
    Reorganize getClient
    
    Cleaning up helper code checking for cache population
    
    Fix event indexer
    
    Tested and working
    
    Add switch to enable / disable cached client
    
    Cleanup compat client, return errors from helpers
    
    Clean up redundant comment
    
    Remove stunnel.go from bad rebase
    
    Put all cached client logic inside feature gate in migcluster_types
    
    Fix log statement with mismatched kv pairs
    djwhatle committed Jun 3, 2021
    Copy the full SHA
    fba6d0b View commit details
    Browse the repository at this point in the history
  2. Copy the full SHA
    9a399d2 View commit details
    Browse the repository at this point in the history
  3. Copy the full SHA
    3403255 View commit details
    Browse the repository at this point in the history