Server configuration: ADR cleaner retry timeout (min)
Applies to: 
SQL Server
Starting with SQL Server 2019 (15.x), this configuration setting is required for accelerated database recovery (ADR). The cleaner is the asynchronous process that wakes up periodically and cleans page versions that aren't needed.
Occasionally the cleaner runs into issues while acquiring object level locks due to conflicts with user workload during its sweep. It tracks such pages in a separate list. ADR cleaner retry timeout (min) controls the amount of time the cleaner would spend exclusively retrying object lock acquisition and cleanup of page before abandoning the sweep. Completion of a sweep with 100 percent success is essential to keep the growth of aborted transactions in the aborted transactions map. If the separate list can't be cleaned up in the prescribed timeout, then the current sweep will be abandoned and the next sweep will start.
| Version | Default value |
|---|---|
| SQL Server 2019 (15.x) | 120 |
| SQL Server 2022 (16.x) and later versions | 15 |
Remarks
The cleaner is single threaded in SQL Server 2019 (15.x), and so one SQL Server instance can work on one database at a time. If the instance has more than one user database with ADR enabled, then don't increase the timeout to a large value. Doing so could delay cleanup on one database while the retry is happening on another database.
Known issue
For SQL Server 2019 (15.x) CU 12 and previous versions, this value might be set to 0. We recommend that you manually reset the value to 120, which is the designed default, using the example in this article.
Examples
The following example sets the cleaner retry timeout to the default value.
EXEC sp_configure 'show advanced options', 1;
RECONFIGURE;
GO
EXEC sp_configure 'ADR cleaner retry timeout', 120;
RECONFIGURE;
GO
Examples
The following example sets the cleaner retry timeout to the default value.
EXEC sp_configure 'show advanced options', 1;
RECONFIGURE;
GO
EXEC sp_configure 'ADR cleaner retry timeout', 15;
RECONFIGURE;
GO