September 9, 2022 at 1:38 am
Hi all,
Just wondering if anyone has seen this in their travels.
I have a client running SQL 2019 STANDARD Edition. They have 70 Basic Availability Groups most of them set to synchronous communication. 1 secondary replica. They recently patched to CU16 on both replicas. Since then they seem to have blocking occur from time to time on the primary with the head blocker exhibiting a HADR_SYNC_COMMIT wait. I have not been able to see if there are any issues on the secondary replica but the queries exhibiting the blocking dont look too bad (small queries returning up to 800 rows). When the head blocker is killed the databases often become unresponsive and we have to failover/failback.
The REDO thread is is parallel mode operation.
The client is adament thy never saw an issue before the patch and want to rollback the CU16. Has anyone come across this type of issue at all?
My feeling is to apply CU17 and set the REDO thread to serial operation.
Any feedback is greatly appreciated.
Scott
September 9, 2022 at 8:28 am
have you been able to intercept the long-running-blocking transaction ?
What is so "special" about it ?
have you checked ( and validated ) the "know issues" for CU16 ?
Validate the "issues fixed" with CU17 . There are a number of AG issues fixes, maybe the issue you're experiencing is fixed too.
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply