LOG-6072: Increase default collector memory limit #2799
Conversation
|
@cahartma: This pull request references LOG-6072 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.8.0" version, but no target version was set. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
openshift-ci-robot
added
the
jira/valid-reference
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cahartma The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci
bot
added
the
approved
|
@cahartma: all tests passed! Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
|
/lgtm |
|
/hold |
openshift-ci
bot
added
the
do-not-merge/hold
Description
We've had a few reports of OOM issues during testing of pre-release 6.0, mainly lokistack and the new otlp output (all log_types). Best solution, we've decided to double the memory limit only, while leaving the other defaults alone. We need more feedback and possibly add otlp to benchmark functional tests.
One other option we can explore before GA is modifying the group_by MaxEvents in the otlp output. (and possibly allowing it to be configurable)
/cc @Clee2691 @vparfonov
/assign @jcantrill
Links