Container Gateway it failed to come online.

Products

• CA API Gateway

Issue/Introduction

We were rebooting the Container Gateway and it failed to come online.

Environment

Gateway 10.1.00_20230901 & Helm chart version is 3.0.15

Cause

The start took longer time and livenessProbe did not get response in specified time, and killed the process. 

 

Resolution

Change the timeout value for the values.yaml file

livenessProbe:
  enabled: true
  type: command
  command: /opt/docker/rc.d/diagnostic/health_check.sh
  initialDelaySeconds: 120
  timeoutSeconds: 1
  periodSeconds: 25
  successThreshold: 1
  failureThreshold: 25

readinessProbe:
  enabled: true
  type: command
  command: /opt/docker/rc.d/diagnostic/health_check.sh
  initialDelaySeconds: 120
  timeoutSeconds: 1
  periodSeconds: 25
  successThreshold: 1
  failureThreshold: 25

Due to the large amount of data for the database,  it took longer time to do the version check operation for the entities.  The possible improvement is to tune the database connection or delete not used the entities.