always on error

  • to day we observed the error and secondary replica is disconnected

    Error: 35217, Severity: 16, State: 1

    The thread pool for AlwaysOn Availability Groups was unable to start a new worker thread because there are not enough available worker threads. This may degrade AlwaysOn Availability Groups performance. Use the "max worker threads" configuration option to increase number of allowable threads.in

    can any one explain the reason and what is the cause of this error occurred

  • I really don't mean this rudely, but have you Googled the error message? There are some helpful blog posts about it already that might be worth a read.

  • worker thread exhaustion can be an issue, can you provide more detail on the number of databases on the instance configured for HADR?

    -----------------------------------------------------------------------------------------------------------

    "Ya can't make an omelette without breaking just a few eggs" 😉

  • Databases are around 10 what is the impact on secondary server due to this issue ?

  • there are many articles available, too many to link. A simple google search will provide you a list

    -----------------------------------------------------------------------------------------------------------

    "Ya can't make an omelette without breaking just a few eggs" 😉

  • Are you running a 32-bit instance by any chance?

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • the server is 64 bit

Viewing 7 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply