staging-ref: Geo LogCursor raises DatabaseConnectionError every 5 minutes

Summary

Every 5 minutes on staging-ref, the Geo LogCursor raise a DatabaseConnectionError.

Steps to reproduce

Look at staging-ref logs (internal).

What is the current bug behavior?

The Geo LogCursor raises an exception every 5 minutes.

What is the expected correct behavior?

The Geo LogCursor does not raise a re-occurring exception every 5 minutes.

Relevant logs and/or screenshots

Results of GitLab environment info

Expand for output related to GitLab environment info

(For installations with omnibus-gitlab package run and paste the output of:
`sudo gitlab-rake gitlab:env:info`)

(For installations from source run and paste the output of:
`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)

Results of GitLab application Check

Expand for output related to the GitLab application check

(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)
(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)
(we will only investigate if the tests are passing)

Possible fixes

Patch release information for backports

Might be inherent to how staging-ref is built, as it wasn't reported on customer instances. No need to backport.

High-severity bug remediation

To remediate high-severity issues requiring an internal release for single-tenant SaaS instances, refer to the internal release process for engineers.