-
Notifications
You must be signed in to change notification settings - Fork 94
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
Redactors in v0.71.1 consume too much memory #1331
Labels
Comments
For context, as first seen in testsuite while bumping troubleshoot to v0.71.1 in kots replicatedhq/kots#4031 And PR relevant to investigation #1291 Potentially helpful tooling #1301 Discussion (internal - all info is summarized above) https://replicated.slack.com/archives/C016DU6CXNE/p1694185342225949 |
@banjoh did you get the images backwards? |
The higher memory consumption can also be reproduced from the CLI:
|
6 tasks
github-project-automation
bot
moved this from In Progress
to Done
in Troubleshoot Roadmap
Sep 15, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug Description
In certain scenarios, running redactor when collector a support bundle can consume a lot of memory leading to OOM signals killing pods.
Here is are memory profiles of this happening in KOTS .
With v0.71.1
With v0.70.3
NOTE: This has not been reproduced when using the CLI.From comments belowv0.71.1
of troubleshootmake build
./bin/support-bundle ./support-bundle.yaml --memprofile=mem.conf --redactors ./redactor.yaml
with support-bundle.yaml and redactor.yamlgo tool pprof -http :8888 -alloc_space mem.prof
will start an http server on port 8888Expected Behavior
Redaction code should not consume excess memory.
Steps To Reproduce
Include the commands to reproduce the issue including any output. Any information that will help us to understand the problem is useful. Feel free to paste long output into a Github gist and include the link here.
To be fleshed
Additional Context
Include the following information.
The text was updated successfully, but these errors were encountered: