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/event-hubs/use-geo-replication.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,27 +22,27 @@ To enable Geo-replication on a namespace during namespace creation:
22
22
23
23
1. Click on ‘Namespace’ to create a new Event Hubs namespace in an Event Hubs cluster in a region with Geo-replication enabled. Provide a name for the namespace and check the Enable Geo-replication box.
24
24
25
-
:::image type="content" source="./media/use-geo-replication/namespace-create.png" alt-text="Dedicated namespace create UI with geo-replication UI":::
25
+
:::image type="content" source="./media/use-geo-replication/namespace-create.png" alt-text="Screenshot of dedicated namespace create UI with geo-replication UI.":::
26
26
27
27
2. Click on Add secondary region and select a secondary region and a corresponding Event Hubs Dedicated cluster running in that region.
28
28
29
-
:::image type="content" source="./media/use-geo-replication/region-selection.png" alt-text="Secondary region and cluster selection in namespace create UI":::
29
+
:::image type="content" source="./media/use-geo-replication/region-selection.png" alt-text="Screenshot of secondary region and cluster selection in namespace create UI.":::
30
30
31
31
3. Select asynchronous or synchronous replication mode as the replication consistency mode. If selecting asynchronous consistency, enter the allowable amount of time the secondary region can lag behind the primary region in minutes.
:::image type="content" source="./media/use-geo-replication/create-replication-consistency.png" alt-text="Screenshot of replication consistency UI in dedicated namespace create UI.":::
34
34
35
35
4. Then click on ‘Create’ to create the Geo Replicated Event Hubs namespace. The deployment takes a couple of minutes to complete.
36
36
5. Once the namespace is created, you can navigate to it and click on "Geo-replication" tab to see your Geo-replication configuration.
37
37
38
-
:::image type="content" source="./media/use-geo-replication/geo-replication.png" alt-text="Geo-replication UI that shows configuration and allows various actions":::
38
+
:::image type="content" source="./media/use-geo-replication/geo-replication.png" alt-text="Screenshot of geo-replication UI that shows configuration and allows various actions.":::
39
39
40
40
## Enable Geo-replication on an existing namespace
41
41
1. Go into the namespace in the portal and click on "Geo-replication".
42
42
2. Click on Add secondary region and select a secondary region and the corresponding Event Hubs Dedicated clusters running in that region.
43
43
3. Select asynchronous or synchronous replication mode as the replication consistency mode. If selecting asynchronous consistency, enter the allowable amount of time the secondary region can lag behind the primary region in minutes.
44
44
45
-
:::image type="content" source="./media/use-geo-replication/geo-replication-consistency.png" alt-text="Replication consistency UI in geo-replication UI":::
45
+
:::image type="content" source="./media/use-geo-replication/geo-replication-consistency.png" alt-text="Screenshot of replication consistency UI in geo-replication UI.":::
46
46
47
47
After a secondary region is added, all of the data held in the primary namespace is replicated to the secondary. Complete replication can take a while depending on various factors with the main one being how much data is in your primary namespace. Users can observe replication progress by monitoring the lag to the secondary region.
48
48
@@ -51,11 +51,11 @@ You can promote your configured secondary region to being the primary region. Wh
51
51
52
52
To initiate a promotion of your secondary region to primary, select failover icon.
53
53
54
-
:::image type="content" source="./media/use-geo-replication/promotion-a.png" alt-text="Promotion UI selection in the geo-replication UI":::
54
+
:::image type="content" source="./media/use-geo-replication/promotion-a.png" alt-text="Screenshot of the promotion UI selection in the geo-replication UI.":::
55
55
56
56
When in the promotion flow, you can select planned or forced. You can also choose to select forced after starting a planned promotion. Enter the word "promote" in the prompt to be able to start the promotion.
57
57
58
-
:::image type="content" source="./media/use-geo-replication/promotion.png" alt-text="Promotion UI in where you can select planned or forced":::
58
+
:::image type="content" source="./media/use-geo-replication/promotion.png" alt-text="Screenshot of the promotion UI in where you can select planned or forced.":::
59
59
60
60
If doing a planned promotion, then once the promotion process is initiated, the new primary rejects any new events until failover is completed. The promotion process repoints the fully qualified domain name(FQDN) for your namespace to the selected region, complete data replication between the two regions and configure the new primary region to be active. Promotion does not require any changes to clients, and that they continue to work after the promotion event.
61
61
@@ -64,7 +64,7 @@ In the case where your primary region goes down completely, you can still perfor
64
64
## Remove a secondary
65
65
To remove a Geo-replication pairing with a secondary, go into "Geo-replication", select the secondary region, and then select remove. At the prompt, enter the word "delete" and then you can delete the secondary.
66
66
67
-
:::image type="content" source="./media/use-geo-replication/remove-secondary.png" alt-text="Remove secondary function in the georeplcation UI":::
67
+
:::image type="content" source="./media/use-geo-replication/remove-secondary.png" alt-text="Screenshot of the remove secondary function in the geo-replcation UI.":::
68
68
69
69
When a secondary region is removed, all of the data that it held is also removed. If you wish to re-enable Geo-replication with that region and cluster, it has to replicate the primary region data all over again.
0 commit comments