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

Update min/max node counts for parser and prometheus #31

Merged
merged 1 commit into from
Aug 24, 2023

Conversation

stephen-soltesz
Copy link
Contributor

@stephen-soltesz stephen-soltesz commented Aug 24, 2023

This change updates the min or max node counts used by the parser and prometheus node pools in the new data-pipeline cluster. The parser default prevented 8 nodes from being created for all parsers, and the prometheus default required wasted nodes. Ideally we want one spare, but two spares is a waste.

Part of:


This change is Reviewable

@stephen-soltesz stephen-soltesz marked this pull request as ready for review August 24, 2023 03:03
Copy link
Contributor

@nkinkade nkinkade left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:lgtm:, but why does modifying max_node_count from 2 to 3 for the parser node pool help with it not being able to create 8 new nodes?

Reviewed 1 of 1 files at r1, all commit messages.
Reviewable status: :shipit: complete! 1 of 1 approvals obtained

Copy link
Contributor Author

@stephen-soltesz stephen-soltesz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, there are three zones per cluster (or node pool) and these autoscaling min/max values appear to apply to each zone. So max 3 nodes * 3 zones is up to 9 nodes. There are 8 in sandbox now for the parser node pool.

Reviewable status: :shipit: complete! 1 of 1 approvals obtained

@stephen-soltesz stephen-soltesz merged commit e82f60d into main Aug 24, 2023
@stephen-soltesz stephen-soltesz deleted the sandbox-soltesz-adjust-minmax branch August 24, 2023 13:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants