Investigate dead connections in gitlab rails connection pools
Gitlab.com, as well as at least one large self-managed customer, shows a high count of dead connections in the rails internal connection pools.
Dead connections must be reaped by the rails connection pool reaper before they can be reused for a new web request, so they add additional pressure to the pgbouncer client connection pool capacity.
Investigate if / how the rails process is failing to return connections to the pool.
issue