search cancel

Registry database is full and not able to start on AWS Cloud

book

Article ID: 255985

calendar_today

Updated On:

Products

CA Application Test

Issue/Introduction

We are facing the issue with registry error on Kubernetes Cluster. Noticed below error in logs


 Connection to the registry database cannot be established. Please make sure the database is running and the credential used to connect to database is valid. 
2022-12-08 17:16:36,508Z (17:16) [main] ERROR System.err           - java.lang.RuntimeException: Connection to the registry database cannot be established. Please make sure the database is running and the credential used to connect to database is valid. 
2022-12-08 17:16:36,508Z (17:16) [main] ERROR System.err           -     at com.itko.lisa.utils.JpaUtil.<init>(JpaUtil.java:504)

Environment

Release : 10.6

Resolution

Execute below commands to see the storage space for registry,

kubectl get pvc

kubectl get pv

          By default Registry pod is allocated with 1GB and with-in the pod, database used by Devtest (lisa.db) size is huge. Due to the large database size, you are facing issue with the database connection.

    For temporary solution, you can delete the lisa.db and allocate more storage space for registry pod and restart the pod. Use external database for registry as a permanent solution for better performance.