Timeline for Connectivity timeout between cluster nodes
Current License: CC BY-SA 3.0
14 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 26, 2017 at 19:20 | comment | added | IMADBA | yes you may need to. Check the instructions. | |
| Oct 26, 2017 at 18:41 | comment | added | SqlNovice | Do i make the change to all the replicas from the properties ? | |
| Oct 26, 2017 at 18:38 | vote | accept | SqlNovice | ||
| Oct 26, 2017 at 18:38 | comment | added | SqlNovice | Appreciate your help! | |
| Oct 26, 2017 at 18:13 | comment | added | IMADBA | Use these instructions:learn.microsoft.com/en-us/sql/database-engine/… | |
| Oct 26, 2017 at 17:24 | comment | added | SqlNovice | Thank you....Just to confirm the session timeout that comes under- Failover cluster manager>Availability Group Properties> Session timeouts> set at 10 Seconds | |
| Oct 26, 2017 at 16:35 | comment | added | IMADBA | If there is no impact to jobload then increase your timeout to 100-200. The errors are expected because your system is undergoing a high load. This was the solution provided by a Microsoft Premier Ticket. | |
| Oct 26, 2017 at 16:12 | comment | added | SqlNovice | SQL server 2012, timeout at 10 seconds. No Job failures during those times. System is on high load from 12 am and onwards ...Just around 1 am almost everyday the primary node faces a connection timeout problem with the other nodes. | |
| Oct 26, 2017 at 15:40 | history | edited | IMADBA | CC BY-SA 3.0 |
added 698 characters in body
|
| Oct 26, 2017 at 15:40 | comment | added | IMADBA | Which version of SQL are you on? What is your timeout set at? What is SQLserver waiting on during those errors? DO you see healthy/unhealthy alerts in databases when you receive this error? Are there any job failures during the error? are there any high loads/ETL loads during the time of error? We had a similar problem in our environment during high ETL loads - the Dbs were available but reported unhealthy/ealthy alerts. We simply increased the timeouts to 100/200 since the alerts were acceptable during these high peak loads. | |
| Oct 26, 2017 at 15:29 | comment | added | SqlNovice | Normally the connection timeout occurs and reconnects within 20 seconds but today it came after 3 minutes | |
| Oct 26, 2017 at 15:08 | comment | added | SqlNovice | The loads are high as frequently the system freezes that time . | |
| Oct 26, 2017 at 15:07 | comment | added | SqlNovice | We are on AAG. Normally everyday around 1 am we see error 35206 that is connection timeout with the replica which prompts error 976 on the secondary...Today the lost connectivity with the secondary remained long enough which the node to be removed from the active node. IF the timeout is short then it shows 976 on the secondary and if long enough it shows 1135 (lost node error). Im not sure where to start | |
| Oct 26, 2017 at 14:55 | history | answered | IMADBA | CC BY-SA 3.0 |