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

Enforce federation prefix to not-allowed caches mapping in matchmaking logic #1750

Open
Saartank opened this issue Nov 18, 2024 · 0 comments
Assignees
Labels
director Issue relating to the director component enhancement New feature or request registry Issue relating to the registry component
Milestone

Comments

@Saartank
Copy link
Collaborator

This is a step towards ensuring federation prefix data does not go into certain caches. Modify the matchmaking logic in the Director so that, given a federation prefix, it queries the registry to get the list of caches not allowed to hold data for that federation prefix and performs the matchmaking accordingly.

@Saartank Saartank added the enhancement New feature or request label Nov 18, 2024
@Saartank Saartank self-assigned this Nov 18, 2024
@Saartank Saartank added director Issue relating to the director component registry Issue relating to the registry component labels Nov 19, 2024
@Saartank Saartank linked a pull request Nov 24, 2024 that will close this issue
@Saartank Saartank added this to the v7.12.0 milestone Dec 2, 2024
@Saartank Saartank removed this from the v7.12.0 milestone Dec 10, 2024
@Saartank Saartank added this to the v7.13.0 milestone Dec 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
director Issue relating to the director component enhancement New feature or request registry Issue relating to the registry component
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant