Bug 1725249
Summary: | Elasticsearch Operator sets resource limits when not requested | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | ewolinet |
Component: | Logging | Assignee: | ewolinet |
Status: | CLOSED ERRATA | QA Contact: | Anping Li <anli> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.1.z | CC: | anli, aos-bugs, ewolinet, jcantril, rmeggins, stwalter, vlaad |
Target Milestone: | --- | ||
Target Release: | 4.1.z | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | No Doc Update | |
Doc Text: | Story Points: | --- | |
Clone Of: | 1725148 | Environment: | |
Last Closed: | 2019-08-28 19:54:45 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1725148 | ||
Bug Blocks: |
Description
ewolinet
2019-06-28 20:13:53 UTC
As discussed with Eric Rich: in my opinion this is worth fixing in 4.1; or else we should specify in the documentation that it is required to be explicit on the limit. Verified using v4.1.9-201907311355. CPU limit is null without explicitly set. nodeSpec: image: image-registry.openshift-image-registry.svc:5000/openshift/ose-logging-elasticsearch5:v4.1.9-201907311355 resources: limits: memory: 2Gi requests: memory: 2Gi Test blocked by https://bugzilla.redhat.com/show_bug.cgi?id=1741753 Verified in 4.1.12 Verified in 4.1.13 Case 1) When no resource in specified resources: {} No CPU limit in ES deployment. resources: limits: memory: 4Gi requests: cpu: 100m memory: 1Gi Case 2) When CPU limit is not set in CRD elasticsearch resources: limits: memory: 2Gi requests: cpu: 200m memory: 2Gi No CPU limit in ES deployment resources: limits: memory: 2Gi requests: cpu: 200m memory: 2Gi Case 3) When CPU limit is set in CRD elasticsearch resources: limits: cpu: 200m memory: 2Gi requests: cpu: 200m memory: 2Gi The CPU limit is specified in ES deployment resources: limits: cpu: 200m memory: 2Gi requests: cpu: 200m memory: 2Gi Case 4) When CPU limit is set as number in CRD elasticsearch resources: limits: cpu: 1 memory: 2Gi requests: cpu: 200m memory: 2Gi The CPU limit is specified in ES deployment resources: limits: cpu: "1" memory: 2Gi requests: cpu: 200m memory: 2Gi Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:2547 |