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

fix: make metadata StatefulSets scale above 0.5 average CPU usage #2114

Merged
merged 1 commit into from
Feb 11, 2022

Conversation

swiatekm
Copy link

Description

All the metadata StatefulSets have requests.cpu set to 500m. Combined with a targetCPUUtilizationPercentage of 50 on the HPA, this meant that they'd try to keep an absolute CPU utilization of 250m = 500m * 0.5.

Changed the CPU utilization on the HPA to 100, so now the absolute utilization is 500m = 500m * 1.0.


Checklist

Remove items which don't apply to your PR.

  • Changelog updated

@swiatekm swiatekm added this to the v2.5 milestone Feb 11, 2022
@swiatekm swiatekm force-pushed the fix/fluentd-hpa-scaling branch from 36edbf7 to a35a6b2 Compare February 11, 2022 10:33
@swiatekm swiatekm marked this pull request as ready for review February 11, 2022 10:33
@swiatekm swiatekm requested a review from a team as a code owner February 11, 2022 10:33
@github-actions github-actions bot added the documentation documentation label Feb 11, 2022
CHANGELOG.md Outdated Show resolved Hide resolved
All the metadata StatefulSets have requests.cpu set to 500m. Combined
with a targetCPUUtilizationPercentage of 50 on the HPA, this meant that
they'd try to keep an absolute CPU utilization of 250m = 500m * 0.5.
Changed the CPU utilization on the HPA to 100, so now the absolute utilization
is 500m = 500m * 1.0.
@swiatekm swiatekm force-pushed the fix/fluentd-hpa-scaling branch from a35a6b2 to 2f0c96d Compare February 11, 2022 11:03
@swiatekm swiatekm requested a review from pmalek-sumo February 11, 2022 11:04
@swiatekm swiatekm merged commit 331d646 into main Feb 11, 2022
@swiatekm swiatekm deleted the fix/fluentd-hpa-scaling branch February 11, 2022 11:39
@sumo-backporter
Copy link
Contributor

The backport to release-v2.5 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-release-v2.5 release-v2.5
# Navigate to the new working tree
cd .worktrees/backport-release-v2.5
# Create a new branch
git switch --create backport-2114-to-release-v2.5
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick --mainline 1 331d6469e5c299bb5b8a943fd01e9cdffa699cc1
# Push it to GitHub
git push --set-upstream origin backport-2114-to-release-v2.5
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-release-v2.5

Then, create a pull request where the base branch is release-v2.5 and the compare/head branch is backport-2114-to-release-v2.5.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants