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

Revisit Filebeat default memory requests/limits #5036

Closed
pebrc opened this issue Nov 10, 2021 · 1 comment · Fixed by #5793
Closed

Revisit Filebeat default memory requests/limits #5036

pebrc opened this issue Nov 10, 2021 · 1 comment · Fixed by #5793
Labels
discuss We need to figure this out >enhancement Enhancement of existing functionality

Comments

@pebrc
Copy link
Collaborator

pebrc commented Nov 10, 2021

We are currently defaulting to 200Mi. However the Filebeats ingesting e2e test cluster data into our monitoring were constantly running into OOM. We should reevaluate whether the current default is still enough with recent version of Filebeat/Metricbeat.

@pebrc pebrc added the discuss We need to figure this out label Nov 10, 2021
@botelastic botelastic bot added the triage label Nov 10, 2021
@pebrc pebrc added the >enhancement Enhancement of existing functionality label Nov 10, 2021
@botelastic botelastic bot removed the triage label Nov 10, 2021
@barkbay
Copy link
Contributor

barkbay commented Nov 15, 2021

It might be a good candidate for the VPA recommender ?
But agreed, we still need to check (with the Beats folks ?) what would be some sane defaults.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discuss We need to figure this out >enhancement Enhancement of existing functionality
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants