starlingx
/
config
Code Issues Proposed changes

Increase rabbitmq pod probe period from 10 to 30s 

To reduce cpu usage on platform cores (especially on AIO), reduce the
frequency of the rabbitmq readiness and liveness probes from every 10s
to 30s.  These probes both run the command "rabbitmqctl status" which
seems to have significant cpu impact.

For reference, the platform rabbitmq process status check runs every
20s.

Partial-Bug: 1837426
Depends-On: https://review.opendev.org/#/c/678052
Change-Id: Ie8eea35b9ed268f4156d1cdc884a6d5004e87018
Signed-off-by: Gerry Kopec <gerry.kopec@windriver.com>
(cherry picked from commit bc62558b37)
This commit is contained in:
Gerry Kopec 2019-08-16 15:55:54 -04:00 committed by Al Bailey
parent 6ce738bf26
commit 1e4df88992
1 changed files with 5 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
kubernetes/applications/stx-openstack/stx-openstack-helm/stx-openstack-helm/manifests/manifest.yaml
View File

@ -311,6 +311,11 @@ data:
anti:
type:
default: requiredDuringSchedulingIgnoredDuringExecution
probes:
readiness:
periodSeconds: 30
liveness:
periodSeconds: 30
# TODO: Revert to upstream defaults once the following LP is resolved:
# https://bugs.launchpad.net/starlingx/+bug/1814595. By changing this PV
# size to 1Gi from the default 265Mi, this avoids the kernel hang from the