Skip to content

Commit dee05a9

Browse files
Merge pull request #217494 from sidramadoss/patch-134
Update stream-analytics-job-reliability.md
2 parents a130ced + 491fa8e commit dee05a9

File tree

1 file changed

+2
-5
lines changed

1 file changed

+2
-5
lines changed

articles/stream-analytics/stream-analytics-job-reliability.md

Lines changed: 2 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -3,10 +3,9 @@ title: Avoid service interruptions in Azure Stream Analytics jobs
33
description: This article describes guidance on making your Stream Analytics jobs upgrade resilient.
44
author: sidramadoss
55
ms.author: sidram
6-
76
ms.service: stream-analytics
87
ms.topic: how-to
9-
ms.date: 06/21/2019
8+
ms.date: 11/07/2022
109
ms.custom: seodec18
1110
---
1211

@@ -16,9 +15,7 @@ Part of being a fully managed service is the capability to introduce new service
1615

1716
## How do Azure paired regions address this concern?
1817

19-
Stream Analytics guarantees jobs in paired regions are updated in separate batches. As a result there is a sufficient time gap between the updates to identify potential issues and remediate them.
20-
21-
_With the exception of Central India_ (whose paired region, South India, does not have Stream Analytics presence), the deployment of an update to Stream Analytics would not occur at the same time in a set of paired regions. Deployments in multiple regions **in the same group** may occur **at the same time**.
18+
Stream Analytics guarantees jobs in paired regions are updated in separate batches. The deployment of an update to Stream Analytics would not occur at the same time in a set of paired regions. As a result there is a sufficient time gap between the updates to identify potential issues and remediate them.
2219

2320
The article on **[availability and paired regions](../availability-zones/cross-region-replication-azure.md)** has the most up-to-date information on which regions are paired.
2421

0 commit comments

Comments
 (0)