Cross-Region Regular Instance Group
Scenarios
Polaris productization supports associating two Polaris standard instances in different regions to form a cross-region standard instance group, enabling cross-region disaster recovery scenarios.
Version Limitations
The instance version is 2.1.0.0 or later.
Basic Edition and Enterprise Edition instances.
Polaris instances with the same instance version and same product specification in different regions. For example, Polaris instances of the basic edition with a 1000-node specification and version 2.1.0.0 in two different regions can be associated to form a cross-region standard instance group and support disaster recovery failover.
Definition
Standard Instance: Newly created Polaris instances are standard Polaris instances by default. Standard instances can be converted to global instances. For using global instances, refer to the documentation "Federated Instance Group".
Operation Steps
To implement a cross-region standard instance group, the following operations are required:
Instance Creation
Log in to Tencent Microservices Platform, create two standard Polaris instances. For details, see Engine Management;
Note:
1. Two instances with identical specifications in different regions.
2. Both instances must have the same product edition (Basic Edition/Enterprise Edition), with an engine version no lower than 2.1.0.0.
Associate to Form a Cross-Region Standard Instance Group
1. Select the Engine Management page of the standard instance intended as the primary region, choose the Instance Architecture tab, and go to the Deployment Architecture page.
2. Click Add Cross-Region Instance, then on the association page, select the target instance (secondary region engine instance) and associate to form a cross-region standard instance group.
3. After association is completed, you can view the cross-region instance group information on the Instance Architecture page of any instance.
Note:
When an association is formed to create a cross-region standard instance group, the Polaris engine instance in the secondary region will restart, which is expected to take 3-5 minutes.
Note:
After the instance in region A associates with the instance in region B to form a cross-region instance group, the instance in region A becomes the primary instance, and the instance in region B becomes the secondary instance.
Bantuan dan Dukungan
Apakah halaman ini membantu?
Anda juga dapat Menghubungi Penjualan atau Mengirimkan Tiket untuk meminta bantuan.
masukan