-
Notifications
You must be signed in to change notification settings - Fork 352
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
Initiate node sizing docs #5018
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suggest we move this guide to the deployment section.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking good.
I'd add a warning "you mileage may vary blabla, use this guide to establish baseline and increase or decrease the resources depending on your workload."
I would remove the file-backed section and create a dedicated metastore section with two subsections one for the service and one for the database. Up to you.
In many setups, the Postgres config will be a bit separate from the QW cluster config (e.g they might have different lifecycles, so live in different terraform scripts). So I think its more readable for the typical ops user to have the sizing suggestions organized accordingly. |
Description
Add a doc entry to help users dimension their QW clusters.
How was this PR tested?
Describe how you tested this PR.