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

add proper support for pool types to first_ready balancer #400

Merged
merged 1 commit into from
Jun 5, 2024

Conversation

demmer
Copy link
Collaborator

@demmer demmer commented Jun 5, 2024

Change the discovery layer to pass in the pool type as part of the Address Attributes, and use that to maintain a map of current connections for each pool type.

Description

Related Issue(s)

Checklist

  • "Backport to:" labels have been added if this change should be back-ported
  • Tests were added or are not required
  • Did the new or modified tests pass consistently locally and on the CI
  • Documentation was added or is not required

Deployment Notes

Change the discovery layer to pass in the pool type as part of the Address
Attributes, and use that to maintain a map of current connections for each pool
type.
@henryr henryr merged commit 2968bc8 into vtgateproxy Jun 5, 2024
32 of 122 checks passed
@henryr henryr deleted the vtgateproxy-firstready-balancer-fix-picker branch June 5, 2024 16:37
dedelala pushed a commit that referenced this pull request Jun 5, 2024
Change the discovery layer to pass in the pool type as part of the Address
Attributes, and use that to maintain a map of current connections for each pool
type.
dedelala pushed a commit that referenced this pull request Jul 30, 2024
Change the discovery layer to pass in the pool type as part of the Address
Attributes, and use that to maintain a map of current connections for each pool
type.
dedelala pushed a commit that referenced this pull request Sep 9, 2024
Change the discovery layer to pass in the pool type as part of the Address
Attributes, and use that to maintain a map of current connections for each pool
type.
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

Successfully merging this pull request may close these issues.

2 participants