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

[Feature] Can LB support consistent hashing? #3428

Open
dandyhuang opened this issue Sep 24, 2024 · 3 comments
Open

[Feature] Can LB support consistent hashing? #3428

dandyhuang opened this issue Sep 24, 2024 · 3 comments
Labels
feature stale Issue has not had recent activity or appears to be solved. Stale issues will be automatically closed

Comments

@dandyhuang
Copy link

Supported implementations:

wrr : Weighted round robin (Kratos Client 内置默认算法)
p2c : Power of two choices
random : Random

@clement2026
Copy link

@dandyhuang Would you describe some of your scenarios where you need a consistent hashing LB policy. This will give us a better understanding of the background and the motivation for implementing it.

@dandyhuang
Copy link
Author

@clement2026 You can understand it as distributing some of the user's redis data and cache to different machines.

Copy link

dosubot bot commented Jan 7, 2025

Hi, @dandyhuang. I'm Dosu, and I'm helping the Kratos team manage their backlog. I'm marking this issue as stale.

Issue Summary:

  • You requested the addition of a consistent hashing load balancing feature to the Kratos framework.
  • The framework currently supports other algorithms like weighted round robin and random selection.
  • @clement2026 asked for specific scenarios where consistent hashing is needed.
  • You explained its usefulness for distributing user data and cache across machines, such as in a Redis setup.

Next Steps:

  • Please let us know if this issue is still relevant to the latest version of the Kratos repository by commenting here.
  • If there is no further activity, this issue will be automatically closed in 7 days.

Thank you for your understanding and contribution!

@dosubot dosubot bot added the stale Issue has not had recent activity or appears to be solved. Stale issues will be automatically closed label Jan 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature stale Issue has not had recent activity or appears to be solved. Stale issues will be automatically closed
Projects
None yet
Development

No branches or pull requests

2 participants