Updated geo-replication exceptions with additional errors, samples, and resolutions

Author: EldertGrootenboer

articles/service-bus-messaging/service-bus-messaging-exceptions-latest.md

@@ -204,37 +204,43 @@ We recommend that you follow these verification steps, depending on the type of
 
 ### ServerBusyException
 
-#### Cause
+#### Causes 
 
 - During asynchronous replication (replication lag greater than zero), the client tries to perform an operation on a service bus entity (queue, topic) or performs a management operation, but the operation cannot be completed because the replication lag between the primary and the secondary regions has exceeded the maximum allowed replication lag in seconds. 
+    - **Example**: The operation is being throttled because with it the new replication lag would reach 38323 seconds, which is greater than the maximum replication lag that was set (300 seconds). The current replication lag for the latest operation being replicated is 0 seconds. 
+- The replication queue for an entity exceeds its maximum size in bytes. The maximum size in bytes for a replication queue is an internal limit set by Service Bus. 
+    - **Example**: Replication queue size 73128000 exceeded threshold 67108864.  
+- In synchronous replication, a request times out while waiting for another request to replicate. 
+    - **Example**: High volume of requests from client application for skarri-stroage-exp1(westus3)/q1:MessagingJournal. Replication to other region(s) is in progress.  
 
 #### Resolution 
 
-The client should back off to give time for the service to process its given workload, then the client should retry. 
+- The client should back off to give time for the service to process its given workload, then the client should retry. Moreover, this could indicate an issue for replication between the primary and secondaries and could be used as an indication that promotion of a secondary should be triggered. 
 
-### TimeoutException 
+### Timeout
 
 #### Cause 
 
 - A timeout exception in Geo DR means that the operation did not complete within the client-provided timeout. 
     - In synchronous replication, an operation’s primary region write and replication to secondary regions are within the scope of the operation’s timeout. 
     - In asynchronous replication, an operation’s primary region write is within the scope of the operation’s timeout, but an operation’s replication to secondary regions is not within the scope of the operation’s timeout. 
+    - **Example**: The operation did not complete within the allocated time 00:01:00 for object message. (ServiceTimeout). 
 
 #### Resolution
 
-The client should retry the operation. 
-
-Note that some steps of a timed-out operation may have been completed. It’s possible that a timed-out operation may have been written to the primary region and some secondary regions. If an operation has been written to the primary region, it will eventually be replicated to all secondary regions regardless of client timeout. 
+- The client should retry the operation. 
+- Note that some steps of a timed-out operation may have been completed. It’s possible that a timed-out operation may have been written to the primary region and some secondary regions. If an operation has been written to the primary region, it will eventually be replicated to all secondary regions regardless of client timeout. 
 
 ### BadRequest 
 
 #### Cause
 
 - During a planned failover, the primary region is temporarily set as read-only in order to allow the secondary region to catch up. If the client attempts a write operation to the primary region while it is in this temporary read-only state, then the client will be receive a BadRequest exception. 
+    - **Example**: Replication role switch in progress, primary replica:<entity-name> is ReadOnly  
 
 #### Resolution
-
-The client must wait for planned failover to complete before write operations will succeed. 
+- The client must wait for planned failover to complete before write operations will succeed. 
+- In case planned failover takes to long, it is possible to trigger a forced failover instead. 
 
 ## Next steps