Skip to content

Commit 1f6a81f

Browse files
authored
Merge pull request #266578 from tfitzmac/0216throttle
added concurrent operation resolution
2 parents 08ed791 + 823e34a commit 1f6a81f

File tree

2 files changed

+16
-2
lines changed

2 files changed

+16
-2
lines changed

articles/azure-resource-manager/management/frequently-asked-questions.yml

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ metadata:
33
title: Azure Resource Manager frequently asked questions
44
description: Answers to common questions about using Azure Resource Manager to manage resources.
55
ms.topic: faq
6-
ms.date: 01/12/2024
6+
ms.date: 02/16/2024
77
content_well_notification:
88
- AI-contribution
99

@@ -40,6 +40,12 @@ sections:
4040
subscription. Settings such as tags, role assignments, and policies aren't automatically transferred from the original resource group to the destination resource group.
4141
You need to reapply these settings to the new resource group. For more information, see [Move resources to new resource group or subscription](./move-support-resources.md).
4242
43+
- name: Resources
44+
questions:
45+
- question: What happens if two operations update the same resource at the same time?
46+
answer: |
47+
Azure Resource Manager detects the conflict and permits only one operation to complete successfully. The other operation fails and returns a 409 conflict error.
48+
If the blocked operation has the correct state, you can retry the operation.``
4349
4450
additionalContent: |
4551
## Related content

articles/azure-resource-manager/management/overview.md

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Azure Resource Manager overview
33
description: Describes how to use Azure Resource Manager for deployment, management, and access control of resources on Azure.
44
ms.topic: overview
5-
ms.date: 02/14/2024
5+
ms.date: 02/16/2024
66
ms.custom: devx-track-arm-template
77
---
88
# What is Azure Resource Manager?
@@ -136,6 +136,14 @@ The resource group location is where Azure Resource Manager stores metadata for
136136

137137
When the resource group's region is unavailable, Azure Resource Manager is unable to update your resource's metadata and blocks your write calls. By colocating your resource and resource group region, you reduce the risk of region unavailability because your resources and metadata exist in one region instead of multiple regions.
138138

139+
## Resolve concurrent operations
140+
141+
When two or more operations try to update the same resource at the same time, Azure Resource Manager detects the conflict and permits only one operation to complete successfully. Azure Resource Manager blocks the other operations and returns an error.
142+
143+
Concurrent resource updates can cause unexpected results. This resolution ensures that your updates are deterministic and reliable. You know the status of your resources and avoid any inconsistency or data loss.
144+
145+
Suppose you have two requests (A and B) that try to update the same resource at the same time. If request A finishes before request B, request A succeeds and request B fails. Request B returns the 409 error. After getting that error code, you can get the updated status of the resource and determine if you want to resend request B.
146+
139147
## Next steps
140148

141149
* To learn about limits that are applied across Azure services, see [Azure subscription and service limits, quotas, and constraints](azure-subscription-service-limits.md).

0 commit comments

Comments
 (0)