Do you have a comment or suggestion to improve SQL Server? We’d love to hear it!

Error 19432 on SQL Server 2017

Receiving steady 19432 errors Always On Availability Groups transport has detected a missing log block for availability database "***". LSN of last applied log block is (***:xxxxx:x). Log scan will be restarted to fix the issue. This is an informational message only. No user action is required.

Symptoms match those described here: https://support.microsoft.com/en-us/help/3201336/low-transaction-throughput-on-always-on-availability-group-primary-rep and here: https://support.microsoft.com/en-us/help/3198760/fix-error-19432-and-time-out-errors-with-sql-server-2016-alwayson-avai for SQL Server 2016, reported as fixed in CU3 for SQL Server 2016. Error 19432 reporting often on secondary replicas coinciding with high HADR_SYNC_COMMIT waits on the primary replica.

Replicas are configured in synchronous mode and live in same data center on same 10GB network

This is showing up in at least CU2 and CU3 for SQL Server 2017. Wondering if the fix made for 2016 made it into 2017 yet or not.

1 vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Anonymous shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    0 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...

      Feedback and Knowledge Base