PostgresSQL DB v15 and health check endpoint

[azhavoro]

Motivation and context

How has this been tested?

Checklist

• I submit my changes into the develop branch
• I have added a description of my changes into CHANGELOG file
• I have updated the documentation accordingly
• I have added tests to cover my changes
• I have linked related issues (read github docs)
• I have increased versions of npm packages if it is necessary (cvat-canvas,
  cvat-core, cvat-data and cvat-ui)

License

• I submit my code changes under the same MIT License that covers the project.
  Feel free to contact the maintainers if that's a concern.

[azhavoro]

/check

[github-actions]

❌ Some checks failed
📄 See logs here

[nmanovic]

@azhavoro , I think a little bit and I propose another solution. Could you please think and give me your opinion?

Let's have a health check endpoint for CVAT. Thus we can use it in our UI and show that the server is not ready yet. Of course, we don't know the reason why, but we can show possible reasons and recommendations, a link to our documentation. I believe it is a step in the right direction.

I will recommend to integrate https://github.com/revsys/django-health-check app. Also we can write small custom plugins and detect some popular problems. For example, OPA isn't running. The problem already can be shown in UI.

[azhavoro]

/check

[github-actions]

❌ Some checks failed
📄 See logs here

[azhavoro]

/check

[github-actions]

✔️ All checks completed successfully
📄 See logs here

[sizov-kirill]

Probably we can try to speed up our tests by simplifying restore.sql script:

I would suggest:

DROP DATABASE IF EXISTS :to WITH FORCE;

instead of current:

SELECT pg_terminate_backend(pg_stat_activity.pid)
FROM pg_stat_activity
WHERE pg_stat_activity.datname = 'cvat' AND pid <> pg_backend_pid();

DROP DATABASE IF EXISTS :to;

But it's necessary to ensure that such solution will give speeding up

[nmanovic]

@azhavoro , healthcheck django package provides a command health_check. It can be used to implement https://docs.docker.com/compose/compose-file/compose-file-v3/#healthcheck. Thus we will have a status for cvat_server.

https://docs.docker.com/engine/reference/builder/#healthcheck

[nmanovic]

Need to document the command as well.

[nmanovic]

Need to improve the initial page

[nmanovic]

No need to write the header one more time in the body. Also at the end there is no a space between the and Upgrade Guide.

[azhavoro]

/check

[github-actions]

❌ Some checks failed
📄 See logs here

[nmanovic]

@azhavoro , why do we need the line now? How is it connected with the patch?

[azhavoro]

@nmanovic I think it's better to remove the HEALTHCHECK command from the Dockerfile for this PR, this currently leads to routing issues related to Traefik container health check behavior traefik/traefik#7732. At the moment I don't find a suitable workaround, so I propose to create a separate issue about adding HEALTHCHECK instruction to CVAT server docker image.

[nmanovic]

OK. Let's do that in this case.

[nmanovic]

LGTM