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 procedure for scale-out, scale-in, server replacement chapters #2001

Closed
wey-gu opened this issue Jul 20, 2022 · 4 comments
Closed

Add procedure for scale-out, scale-in, server replacement chapters #2001

wey-gu opened this issue Jul 20, 2022 · 4 comments

Comments

@wey-gu
Copy link
Contributor

wey-gu commented Jul 20, 2022

The procedure should be provided in a searchable manner :)

For scale-in, the key step is to balance data remove.

https://docs.nebula-graph.io/3.1.0/synchronization-and-migration/2.balance-syntax/

note: we already have scaling chapters for the nebulagraph k8s operator.

@wey-gu
Copy link
Contributor Author

wey-gu commented Jul 20, 2022

@abby-cyber
Copy link
Contributor

abby-cyber commented Jul 22, 2022

ref on scale-in: https://discuss.nebula-graph.com.cn/t/topic/9213/2

No commands are provided to scale a cluster. User can manually scale a cluster that is mentioned in
https://docs.nebula-graph.io/3.1.0/20.appendix/0.FAQ/#how_to_scale_out_or_scale_in_enterprise_edition_only

@wey-gu
Copy link
Contributor Author

wey-gu commented Jul 22, 2022

@abby-cyber got it, this information is the one! But it's actually not that easy for user(to seek for how to scale-in/out by searching in docs), thus I think adding a chapter may still worth it?

Screen Shot 2022-07-22 at 11 52 17 AM

@abby-cyber
Copy link
Contributor

Yeah, will consider it after the auto scaling commands are developed. Currently, uses can refer to FAQ for manual scaling operations.

Yeah, will consider it after the auto scaling commands are developed. Currently, uses can refer to FAQ for manual scaling operations.

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

2 participants