Merge pull request #233166 from seesharprun/cosmos-nosql-revamp-troubleshoot-service

Cosmos DB | Revamp troubleshooting article

Author: v-regandowner

articles/cosmos-db/nosql/troubleshoot-service-unavailable.md

@@ -2,24 +2,25 @@
 title: Troubleshoot Azure Cosmos DB service unavailable exceptions
 description: Learn how to diagnose and fix Azure Cosmos DB service unavailable exceptions.
 author: seesharprun
+ms.author: sidandrews
+ms.reviewer: mjbrown
 ms.service: cosmos-db
 ms.subservice: nosql
-ms.date: 08/31/2022
-ms.author: sidandrews
 ms.topic: troubleshooting
-ms.reviewer: mjbrown
+ms.date: 04/03/2023
 ---
 
 # Diagnose and troubleshoot Azure Cosmos DB service unavailable exceptions
+
 [!INCLUDE[NoSQL](../includes/appliesto-nosql.md)]
 
 The SDK wasn't able to connect to Azure Cosmos DB. This scenario can be transient or permanent depending on the network conditions.
 
-It is important to make sure the application design is following our [guide for designing resilient applications with Azure Cosmos DB SDKs](conceptual-resilient-sdk-applications.md) to make sure it correctly reacts to different network conditions. Your application should have retries in place for service unavailable errors.
+It's important to make sure the application design is following our [guide for designing resilient applications with Azure Cosmos DB SDKs](conceptual-resilient-sdk-applications.md) to make sure it correctly reacts to different network conditions. Your application should have retries in place for service unavailable errors.
 
 When evaluating the case for service unavailable errors:
 
-* What is the impact measured in volume of operations affected compared to the operations succeeding? Is it within the service SLAs?
+* What is the effect measured in volume of operations affected compared to the operations succeeding? Is it within the service SLAs?
 * Is the P99 latency / availability affected?
 * Are the failures affecting all your application instances or only a subset? When the issue is reduced to a subset of instances, it's commonly a problem related to those instances.
 
@@ -29,15 +30,16 @@ The following list contains known causes and solutions for service unavailable e
 
 ### Verify the substatus code
 
-In certain conditions, the HTTP 503 Service Unavailable error will include a substatus code that helps to identify the cause.
+In certain conditions, the HTTP 503 Service Unavailable error includes a substatus code that helps to identify the cause.
 
-| SubStatus Code | Description |
+| Substatus Code | Description |
 |----------|-------------|
 | 20001 | The service unavailable error happened because there are client side [connectivity issues](#client-side-transient-connectivity-issues) (failures attempting to connect). The client attempted to recover by [retrying](conceptual-resilient-sdk-applications.md#timeouts-and-connectivity-related-failures-http-408503) but all retries failed. |
 | 20002 | The service unavailable error happened because there are client side [timeouts](troubleshoot-dotnet-sdk-request-timeout.md#troubleshooting-steps). The client attempted to recover by [retrying](conceptual-resilient-sdk-applications.md#timeouts-and-connectivity-related-failures-http-408503) but all retries failed. |
 | 20003 | The service unavailable error happened because there are underlying I/O errors related to the operating system. See the exception details for the related I/O error. |
 | 20004 | The service unavailable error happened because [client machine's CPU is overloaded](troubleshoot-dotnet-sdk-request-timeout.md#high-cpu-utilization). |
-| 20005 | The service unavailable error happened because client machine's threadpool is starved. Verify any potential [blocking async calls in your code](https://github.com/davidfowl/AspNetCoreDiagnosticScenarios/blob/master/AsyncGuidance.md#avoid-using-taskresult-and-taskwait). |
+| 20005 | The service unavailable error happened because client machine's thread pool is starved. Verify any potential [blocking async calls in your code](https://github.com/davidfowl/AspNetCoreDiagnosticScenarios/blob/master/AsyncGuidance.md#avoid-using-taskresult-and-taskwait). |
+| 20006 | The connection between the service and client was interrupted or terminated in an unexpected manner. |
 | >= 21001 | This service unavailable error happened due to a transient service condition. Verify the conditions in the above section, confirm if you have retry policies in place. If the volume of these errors is high compared with successes, reach out to Azure Support. |
 
 ### The required ports are being blocked