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

Dynamic management of providers priority #1183

Open
alambare opened this issue Jun 4, 2024 · 0 comments
Open

Dynamic management of providers priority #1183

alambare opened this issue Jun 4, 2024 · 0 comments
Labels
enhancement New feature or request server Server-mode related

Comments

@alambare
Copy link
Collaborator

alambare commented Jun 4, 2024

Current implementation sort providers by a priority defined in configuration.

This leaves few limits:

  • we always hit the quotas of the same provider first
  • in case of a provider malfunction, the quality of service is impacted and the system does not react automatically

We could develop a provider priority orchestrator whose job would be to adapt the priority depending of the server behavior.
For example:

  1. A provider stops responding. After a number of failed requests its priority is lowered (the provider could even be set unavailable)
  2. A provider quotas got hit and the bandwidth is reduced. Below a certain target, the priority of the provider is lowered
  3. Automatic rebalancing of provider priorities after multiple requests to spread the load

The providers should be checked after some time to reassess their situation.

The algorithm is left to be designed in this issue

@alambare alambare added enhancement New feature or request server Server-mode related labels Jun 4, 2024
@alambare alambare changed the title [server] dynamic management of providers priority Dynamic management of providers priority Jun 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request server Server-mode related
Projects
None yet
Development

No branches or pull requests

1 participant