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

DefaultEndpointRouter results uneven autoscaling in mutiple endpoints scenario #1839

Closed
bjqian opened this issue Oct 12, 2023 · 1 comment
Closed
Assignees

Comments

@bjqian
Copy link
Contributor

bjqian commented Oct 12, 2023

Describe the Issue

When utilizing two SignalR instances in multiple endpoints scenario:

  • SignalR A: Autoscaling is enabled at 80% of quota usage
  • SignalR B: Autoscaling is enabled at 80% of quota usage

An issue arises after SignalR A is scaled up: SignalR B is less likely to scale up. This occurs because the DefaultEndpointRouter uses a weighted routing method, which routes connections based on the remaining connection quota of each endpoint.

Expected Behavior

The DefaultEndpointRouter should ensure that instances scale more evenly when autoscaling is enabled.

@bjqian bjqian self-assigned this Oct 12, 2023
@bjqian
Copy link
Contributor Author

bjqian commented Oct 16, 2023

Normalize the DefaultEndpointRouter weight using unit:

private ServiceEndpoint GetEndpointAccordingToWeight(ServiceEndpoint[] availableEndpoints)

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

No branches or pull requests

1 participant