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

[Features] support heterogeneous component configuration for ClusterSpec.Shardings API #8443

Open
starnop opened this issue Nov 13, 2024 · 1 comment

Comments

@starnop
Copy link
Contributor

starnop commented Nov 13, 2024

What is the user interaction of your feature
A concise description of user interactions or user stories of your feature request

Scenario one, takes the specified pod instance offline, and the offline instance should be recorded in the component configuration of the corresponding shard.

Scenario two, horizontal scale up some instances for a shard due to traffic imbalance

Scenario three, vertical scale up some instances for a shard due to traffic imbalance

Scenario four, instance replacement requires scaling up before scaling down.

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

If this is a new feature, please describe the motivation and goals.
A clear and concise description of why you want to happen, link the design doc if possible

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

Copy link

This issue has been marked as stale because it has been open for 30 days with no activity

@github-actions github-actions bot added the Stale label Dec 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants