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

[DISCUSSION] ShardingSphere AutoScaling #489

Open
mlycore opened this issue Jul 6, 2024 · 0 comments
Open

[DISCUSSION] ShardingSphere AutoScaling #489

mlycore opened this issue Jul 6, 2024 · 0 comments

Comments

@mlycore
Copy link
Contributor

mlycore commented Jul 6, 2024

For stateful database connections between applications and ShardingSphere, it is always hard to scale the proxy to handle more long connections. If we scale the proxy horizontally, we cannot move the current long connection causing heavy load to move to new instances. The complexity and cost brought by this solution are way higher than letting it go. If we scale the proxy vertically, we can increase the CPU threshold and resolve overhead caused by computing. However, this idea cannot move to memory, since currently JVM is not capable of adjusting heap memory size in runtime.

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