When you use Always On Availability Groups in Microsoft SQL Server 2016 or 2017, the parallel recovery of the readable secondary replica is suspended if there are concurrent read-only queries on the same replica, and you receive the following error message:
Date\Time SPID A time-out occurred while waiting for buffer latch -- type 4, bp 000000E66DA93540, page PageID, stat 0xb, database id: DatabaseID, allocation unit Id: UnitID, task TaskID, waittime 300 seconds, flags 0x1018, owning task TaskID. Not continuing to wait.
This issue is fixed in the following cumulative updates for SQL Server:
To work around this issue, use one of the following methods:
Avoid the primary replica and secondary replica working on the same table at the same time.
Set a query time-out to exit the query when it has been executed for 1 or 2 minutes.
Reduce the MAXDOP.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Learn about the terminologythat Microsoft uses to describe software updates.