Understanding about restarting QMetry services, their dependencies, and impact

This article helps you understand the QMetry services - their interdependencies, and the impact on restart. You will also get complete information about the order of Service Restart and dependencies among the QMetry Services.

1. Order of Services Restart :

   • All the QMetry services should be restarted in the order given below.

     • QMetry DB (docker) ⟶ QMetry App (docker) ⟶ QMetry Reports DB (docker) ⟶ QMetry Reports App (docker).

       1. docker restart qmetry_rds_1 qmetry_app_1

       2. docker restart qmetry-reports-db qmetry-reports

2. Dependencies among the Services :

   • Reports Services need QMetry App and DB services to be running.

   • App services need to first have DB services running.

     • i.e. QMetry App should be started after starting QMetry DB.

       1. docker stop qmetry_app_1 qmetry_rds_1

       2. docker start qmetry_rds_1

       3. docker start qmetry_app_1

     • And QMetry Reports App should be started after starting the Reports DB.

       1. docker stop qmetry-reports qmetry-reports-db

       2. docker start qmetry-reports-db

       3. docker start qmetry-reports

   • The App server (tomcat) needs DB services to be running to start the application.

3. Impact of restarting services individually :

   • If the QMetry app and/or DB services are restarted individually, the entire QMetry site will not be accessible.

   • If QMetry Reports and/or Reports DB services are restarted individually - custom reports will not work and data from the QMetry app to custom reports DB stops syncing.

   • Restarting the QMetry Reports app/DB impacts only custom reports and not system reports.