When the DB cpu utilization is 100%

try restarting the pods one by one

kubectl rollout restart deployment hmpps-interventions-service-dashboard -n hmpps-interventions-prod
kubectl rollout restart deployment hmpps-interventions-service-api -n hmpps-interventions-prod
kubectl rollout restart deployment hmpps-interventions-ui -n hmpps-interventions-prod
kubectl rollout restart deployment hmpps-interventions-service-performance-report -n hmpps-interventions-prod

If the above commands does not bring the db cpu utilization down, trying scaling down and scale up the pods

commands for scaling down

kubectl scale deployment hmpps-interventions-service-dashboard -n hmpps-interventions-prod --replicas=0
kubectl scale deployment hmpps-interventions-service-api -n hmpps-interventions-prod --replicas=0
kubectl scale deployment hmpps-interventions-ui -n hmpps-interventions-prod --replicas=0
kubectl scale deployment hmpps-interventions-service-performance-report -n hmpps-interventions-prod --replicas=0

commands for scaling up

kubectl scale deployment hmpps-interventions-service-dashboard -n hmpps-interventions-prod --replicas=2
kubectl scale deployment hmpps-interventions-service-api -n hmpps-interventions-prod --replicas=3
kubectl scale deployment hmpps-interventions-ui -n hmpps-interventions-prod --replicas=3
kubectl scale deployment hmpps-interventions-service-performance-report -n hmpps-interventions-prod --replicas=1

This page was last reviewed on 14 November 2023. It needs to be reviewed again on 14 November 2024 by the page owner #interventions-dev .

This page was set to be reviewed before 14 November 2024 by the page owner #interventions-dev. This might mean the content is out of date.