Merge pull request #27736 from AbdullahMSFT/patch-7

prmerger-automator[bot] · web-flow · commit ee8ffd89fa53 · 2023-08-02T20:42:47.000Z
Update change-the-session-timeout-period-for-an-availability-replica-…
diff --git a/docs/database-engine/availability-groups/windows/change-the-session-timeout-period-for-an-availability-replica-sql-server.md b/docs/database-engine/availability-groups/windows/change-the-session-timeout-period-for-an-availability-replica-sql-server.md
@@ -51,7 +51,7 @@ helpviewer_keywords:
   
      MODIFY REPLICA ON '*instance_name*' WITH ( SESSION_TIMEOUT =*seconds* )  
   
-     where *group_name* is the name of the availability group, *instance_name* is the name of the server instance that hosts the availability replica to be modified, and *seconds* specifies the minimum number of seconds that the replica must wait before applying log to databases when acting as a secondary replica. The default is 0 seconds, which indicates that there is no apply delay.  
+     where *group_name* is the name of the availability group, *instance_name* is the name of the server instance that hosts the availability replica to be modified, and *seconds* specifies how many seconds the availability replica waits for a ping response from a connected replica before considering the connection to have failed. By default, a replica waits 10 seconds for a ping response.  
   
      The following example, entered on the primary replica of the `AccountsAG` availability group, changes the session-timeout value to `15` seconds for the replica located on the `INSTANCE09` server instance.  
   
