Implement Prohibited Caches for Federation Prefixes #1769
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR implements a step towards enabling users to configure a list of caches where data should not propagate for a given federation prefix.
Changes Introduced:
Modify Registry Database:
prohibited_caches
, in thenamespace
table to store prohibited caches for federation prefixes. This column stores a list of prohibited cache hostnames.Adjust Registry Endpoints:
GET /api/v1.0/registry/namespaces/prohibitedCaches
that returns a map of federation prefixes to their corresponding list of prohibited cache hostnames.registry
andregistry_ui
namespace endpoints to include prohibited caches data in their responses.Add Goroutine in Director:
Director.ProhibitedCachesRefreshInterval
, to control the time interval at which this goroutine sends requests to the registry endpoint.Update Matchmaking Logic: