Bug 1391719 - High CPU consumption with liveness and readines probes for EAP image
Summary: High CPU consumption with liveness and readines probes for EAP image
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: ImageStreams
Version: 3.3.0
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: ---
Assignee: kconner
QA Contact: Tomas Schlosser
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-03 20:25 UTC by Miheer Salunke
Modified: 2020-08-13 08:40 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
undefined
Clone Of:
Environment:
Last Closed: 2017-02-20 15:13:53 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker CLOUD-834 0 Major Closed Rewrite probes 2020-09-18 03:27:50 UTC
Red Hat Knowledge Base (Solution) 2899151 0 None None None 2017-12-01 19:03:15 UTC

Description Miheer Salunke 2016-11-03 20:25:37 UTC
Description of problem:

When configuring readiness and liveness probe with the following, in one node we see high CPU consumption.


livenessProbe:
            exec:
              command: [/bin/bash, '-c', /opt/eap/bin/livenessProbe.sh]
            initialDelaySeconds: 30
            timeoutSeconds: 30
            periodSeconds: 10
            successThreshold: 1
            failureThreshold: 3
          readinessProbe:
            exec:
              command: [/bin/bash, '-c', /opt/eap/bin/readinessProbe.sh]
            initialDelaySeconds: 30
            timeoutSeconds: 30
            periodSeconds: 10
            successThreshold: 1
            failureThreshold: 3



Version-Release number of selected component (if applicable):
OCP 3,2.0

How reproducible:
On customer side

Steps to Reproduce:
1. 
2.
3.

Actual results:


Expected results:


Additional info:

Comment 20 Ben Parees 2017-02-20 15:13:53 UTC
closing as this is being tracked in JIRA now, which is the mechanism for middleware image issues.


Note You need to log in before you can comment on or make changes to this bug.