Skip to content

Commit 19f6d89

Browse files
authored
Small fix
1 parent c1ceee0 commit 19f6d89

File tree

1 file changed

+6
-3
lines changed

1 file changed

+6
-3
lines changed

articles/sql-database/sql-database-managed-instance.md

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -179,14 +179,17 @@ Managed instances are available during update operations but there is a short do
179179

180180
Managed instance management operations can affect other management operations of the instances placed inside the same virtual cluster. This includes following:
181181

182-
- **Long running restore operations** in a virtual cluster will put on hold other instance creation or scaling operation in the same subnet.
182+
- **Long running restore operations** in a virtual cluster will put on hold other instance creation or scaling operation in the same subnet.
183+
183184
Example: if there is long running restore operation and there is create or scale request in the same subnet, this request will take longer to complete as it will wait for restore operation to complete before it continues.
184185

185-
- **Subsequent instance creation or scaling** operation is put on hold by previously initiated instance creation or instance scale that initiated virtual cluster resize
186+
- **Subsequent instance creation or scaling** operation is put on hold by previously initiated instance creation or instance scale that initiated virtual cluster resize.
187+
186188
Example: if there are multiple create and/or scale requests in the same subnet under the same virtual cluster, and one of them initiates virtual cluster resize, all requests that were submitted 5+ minutes after the one that required virtual cluster resize will last longer than expected as these requests will have to wait for the resize to complete before resuming.
187189

188190
- **Create/scale operations submitted in 5 minute window** will be batched and executed in parallel
189-
Result: Only one virtual cluster resize will be performed for all operations submitted in 5 minute window (measuring from the moment of executing the first operation request). In case that another request is submitted more than 5 minutes after submitting the first one, it will wait for virtual cluster resize to complete before execution starts.
191+
192+
Example: Only one virtual cluster resize will be performed for all operations submitted in 5 minute window (measuring from the moment of executing the first operation request). In case that another request is submitted more than 5 minutes after submitting the first one, it will wait for virtual cluster resize to complete before execution starts.
190193

191194
> [!IMPORTANT]
192195
> All management operations are part of deployment automation process and any operation that is put on hold is automatically resumed after all conditions are met. There is no user action needed.

0 commit comments

Comments
 (0)