You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-arc/data/reprovision-replica.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,15 +15,15 @@ ms.date: 10/05/2022
15
15
16
16
This article describes how to provision a new replica to replace an existing replica in Azure Arc-enabled SQL Managed Instance.
17
17
18
-
When you reprovision a replica, you rebuild a new managed instance replica for an Azure Arc-enabled SQL Managed Instance deployment. Use this task to replace a replica that is failing to synchronize, for example, due to corruption of the data on the persistent volumes (PV) for that instance, or due to some recurring SQL issue, for example.
18
+
When you reprovision a replica, you rebuild a new managed instance replica for an Azure Arc-enabled SQL Managed Instance deployment. Use this task to replace a replica that is failing to synchronize, for example, due to corruption of the data on the persistent volumes (PV) for that instance, or due to some recurring SQL issue.
19
19
20
-
Support for reprovisioning of a replica is provided only via `az` CLI and kube-native. You can't reprovision a replica from Azure portal.
20
+
You can reprovision a replica with `az` CLI and Kubernetes tools. You can't reprovision a replica from the Azure portal.
21
21
22
22
## Prerequisites
23
23
24
24
Reprovisioning can only be performed on a multi-replica instance.
25
25
26
-
## Request a reprovision replica
26
+
## Reprovision a replica
27
27
28
28
Request provisioning [via `az` CLI](#via-az-cli) or [via `kubectl`](#via-kubectl).
29
29
@@ -41,7 +41,7 @@ For example, to reprovision replica 2 of instance `mySqlInstance` in namespace `
41
41
az sql mi-arc reprovision-replica -n mySqlInstance-2 -k arc --use-k8s
42
42
```
43
43
44
-
The command runs until completion, at which point the console returns the name of the kubernetes task:
44
+
The command runs until completion, at which point the console returns the name of the Kubernetes task:
45
45
46
46
```output
47
47
sql-reprov-replica-mySqlInstance-2-1664217002.376132 is Ready
@@ -83,7 +83,7 @@ to view all reprovision tasks.
83
83
84
84
## Via kubectl
85
85
86
-
To reprovision with `kubectl`, create a custom resource definition (CRD). To create a CRD to reprovision, you can create a .yaml file with this structure:
86
+
To reprovision with `kubectl`, create a custom resource. To create a custom resource to reprovision, you can create a .yaml file with this structure:
- The task rejects attempts to reprovision the current primary replica. If the current primary replica is corrupted and in need of reprovisioning, fail over to a different primary, and then request the reprovisioning.
126
+
- The task rejects attempts to reprovision the current primary replica. If the current primary replica is corrupted and in need of reprovisioning, fail over to a different replica, and then request the reprovisioning.
127
127
128
-
- Reprovisioning of multiple replicas in the same instance runs serially. The tasks queue and be held in `Creating` state until the currently active task finishes **and is deleted**. There's no auto-cleanup of a completed task, so this serialization will affect you even if you run the `az sql mi-arc reprovision-replica` command synchronously and wait for it to complete before requesting another reprovision. In all cases, you have to remove the task via `kubectl` before another reprovision on the same instance can run.
128
+
- Reprovisioning of multiple replicas in the same instance runs serially. The tasks queue and are held in `Creating` state until the currently active task finishes **and is deleted**. There's no auto-cleanup of a completed task, so this serialization will affect you even if you run the `az sql mi-arc reprovision-replica` command synchronously and wait for it to complete before requesting another reprovision. In all cases, you have to remove the task via `kubectl` before another reprovision on the same instance can run.
129
129
130
130
More details about serialization of reprovision tasks: If you have multiple requests to reprovision a replica in one instance, you may see something like this in the output from a `kubectl get SqlManagedInstanceReprovisionReplicaTask`:
|Arc Data extension for Azure Data Studio<br/>`arc`<br/>`azcli`|*No Changes*<br/>1.5.4 ([Download](https://aka.ms/ads-arcdata-ext))</br>1.5.4 ([Download](https://aka.ms/ads-azcli-ext))|
29
+
|Arc Data extension for Azure Data Studio<br/>`arc`<br/>`azcli`|*No Changes*<br/>1.5.4 </br>1.5.4 |
0 commit comments