Status: Closed (View Workflow)
Affects Version/s: 4.14.12, 5.16.11, 7.6.5, 7.11.2, 6.10.10
When a backup is kicked off (whether using the backup client or DIY scripts), and when in-app database migration is performed, the system starts out by draining in-use database connections and waiting until the pool is idle.
A change made in Bitbucket Server/Data Center 4.14 introduced a wrapper around the DataSource which the draining code was not updated to handle. As a result, database connections are not drained and backup/migration are allowed to continue with some number of connections potentially still in use.
- Put the system into maintenance mode
- Trigger a backup
Database connections are drained.
Database connections are not drained.
The following warning appears in the logs:
There is no workaround for this issue; it requires an in-code fix.