Bug 1725148
| Summary: | Elasticsearch Operator sets resource limits when not requested | |||
|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Jeff Cantrill <jcantril> | |
| Component: | Logging | Assignee: | ewolinet | |
| Status: | CLOSED ERRATA | QA Contact: | Anping Li <anli> | |
| Severity: | high | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | 4.1.z | CC: | aos-bugs, ewolinet, rmeggins | |
| Target Milestone: | --- | |||
| Target Release: | 4.2.0 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | No Doc Update | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1725249 (view as bug list) | Environment: | ||
| Last Closed: | 2019-10-16 06:32:46 UTC | Type: | Bug | |
| 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: | ||||
| Bug Blocks: | 1725249 | |||
Verified using ose-cluster-logging-operator:v4.2.0-201907232219. The resource are created without cpu limit.
resources:
limits:
memory: 16Gi
requests:
cpu: "1"
memory: 16Gi
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:2922 |
Description of problem:While standing up Cluster Logging, the Elasticsearch instance was under resourced because it was given an artificial CPU limit. This led to issues like: [2019-06-28T13:38:19,931][WARN ][c.f.s.s.t.SearchGuardSSLNettyTransport] [elasticsearch-cdm-yh9fg40h-1] write and flush on the network layer failed (channel: [id: 0x32462b90, L:/10.128.2.11:56430 - R:elasticsearch-cluster.openshift-logging.svc/172.30.143.44:9300]) javax.net.ssl.SSLException: SSLEngine closed already at io.netty.handler.ssl.SslHandler.wrap(...)(Unknown Source) ~[?:?] [2019-06-28T13:38:26,634][ERROR][c.f.s.s.t.SearchGuardSSLNettyTransport] [elasticsearch-cdm-yh9fg40h-1] SSL Problem Received close_notify during handshake javax.net.ssl.SSLException: Received close_notify during handshake Version-Release number of selected component (if applicable): cluster logging operator 4.1.3 How reproducible: Always Steps to Reproduce: 1. 2. 3. Actual results: EO created resource spec of: resources: limits: cpu: 100m memory: 4Gi requests: cpu: 100m memory: 4Gi from the CLO generated ES instance of: resources: requests: cpu: 100m memory: 4Gi Expected results: The pod spec should only define resource request values Additional info: