This topic guides you through the MSHA Quick Start. MSHA supports multi-active disaster recovery for various architectures and components. Using a demo application, this guide demonstrates active zone-redundancy and cross-region active-active application architectures. You will experience multi-active capabilities at both the ingress and data layers.
Prerequisites
Complete the basic configuration described in Permission requirements. Otherwise, the Quick Start will not function correctly.
The multi-active instances and demo application nodes created during this Quick Start are free. However, resources such as Elastic Compute Service (ECS) and Microservices Engine (MSE) are automatically created in your account to deploy the multi-active application. These resources may incur fees.
The Quick Start creates pay-as-you-go resources. Ensure that your account balance is greater than CNY 100. For more information, see Pay-as-you-go.
Quick Start
Navigate to the MSHA console and click to open the Quick Start page.
The at the top of the page shows your progress, a description of the current step, and its status.
Cloud resource checklist:
Resource | Architecture type | Specification | Description |
Virtual Private Cloud VPC |
| None | Supports automatic creation or using an existing VPC. |
Virtual Private Cloud vSwitch |
| None | Supports automatic creation or using an existing vSwitch. |
Virtual Private Cloud VPC peering connection |
| Gold | Automatic creation only. Used to connect the networks of VPCs in two regions. The CIDR blocks of the source and destination VPCs must be different. |
Elastic Compute Service ECS |
| The demo application requires more than 1 GB of memory | Automatic creation only. Automatically created instances have a minimum of 1 vCPU and 2 GB of memory, and a maximum of 32 GB of memory. If the required specifications are not available in the selected zone, choose a different zone. Note Created only if you check "Ingress layer component". |
Elastic Compute Service Security group |
| Basic security group | Supports automatic creation or using an existing security group. |
Microservices Engine Registry and configuration center |
| Developer Edition 1 vCPU, 2 GB 1 node | Automatic creation only. |
Microservices Engine Cloud-native gateway |
| Standard Edition 2 vCPUs, 4 GB 1 node | Automatic creation only. Important You must manually create the msha-router custom plugin. For more information, see Manage cloud-native gateway ingress clusters. Note Created only if you check "Ingress layer component". |
Data Transmission Service Data synchronization |
| micro | Automatic creation only. |
1. Initialization
Go to to begin onboarding.
Recommended regions
China (Beijing) - Zone F and Zone K
China (Hangzhou) - Zone I and Zone J
Configurations for this step are not submitted until you click Next. You can refresh the page to reconfigure at any time.
All resources created by the Quick Start are private network resources.
Do not delete the created resources before completing Step 5 to prevent failures.
You must use the same creation method for all resources: either 'Automatic creation' or 'Select existing...'.
Active zone-redundancy
Configuration item | Configuration | Description |
Module activation | None | This item confirms that you have activated the required modules. The product automatically detects your activation status. Follow the prompts to activate the corresponding components.
Note If you only want to experience the ingress layer and have not activated the data layer module, you can proceed even if the status is "Data layer component not activated". |
Architecture type |
| This item selects the disaster recovery architecture for the experience. You can select only one architecture for each session. For more information, see Multi-active architectures. |
Select region |
| This item selects the region and zones for the active zone-redundancy architecture deployment. It is used to create the LDC, unit, and cell where the experience instance resides. The first zone is the primary zone by default, and the second zone is the secondary zone by default. For more information, see Business LDC. |
Create VPC |
| This item selects the VPC where the resources reside. If you use an automatically created VPC, no selection is needed. If you use an existing VPC, click "Select existing VPC" and check the VPC to use. |
Create security group |
| This item selects the security group where the resources reside. If you use an automatically created security group, no selection is needed. If you use an existing security group, click "Select existing security group" and check the security group to use. |
Create vSwitch |
| This item selects the vSwitch where the resources reside. If you use an automatically created vSwitch, no selection is needed. If you use an existing vSwitch, click "Select existing vSwitch" and check the vSwitch to use. |
Select multi-active components |
| This item selects the components to experience for active zone-redundancy. If you do not want to experience any features and only want to create an empty multi-active instance, no selection is needed. If you want to experience the ingress layer, check this option. |
Cross-region active-active application
Configuration item | Configuration | Description |
Module activation | None | This item confirms that you have activated the required modules. The product automatically detects your activation status. Follow the prompts to activate the corresponding components.
|
Architecture type |
| This item selects the disaster recovery architecture for the experience. You can select only one architecture for each session. For more information, see Multi-active architectures. |
Select primary region |
| This item selects the primary region and zone for the cross-region active-active application architecture deployment. It is used to create the LDC and unit where the experience instance resides. For more information, see Business LDC. |
Select secondary region |
| This item selects the secondary region and zone for the cross-region active-active application architecture deployment. It is used to create the LDC and unit where the experience instance resides. For more information, see Business LDC. |
Create VPC |
| This item selects the VPC where the resources reside. If you use an automatically created VPC, no selection is needed. If you use an existing VPC, click "Select existing VPC" and check the VPC to use. Warning If you select "Use existing VPC", ensure that the CIDR blocks of the two VPCs are different. Otherwise, the network connection may fail. |
Create security group |
| This item selects the security group where the resources reside. If you use an automatically created security group, no selection is needed. If you use an existing security group, click "Select existing security group" and check the security group to use. |
Create vSwitch |
| This item selects the vSwitch where the resources reside. If you use an automatically created vSwitch, no selection is needed. If you use an existing vSwitch, click "Select existing vSwitch" and check the vSwitch to use. |
Select multi-active components |
| This item selects the components to experience for the cross-region active-active application. If you want to experience the ingress layer, check this option. The data layer component is required and checked by default. |
Click Next. The status of Step 1 changes to In progress. When the status changes to Completed, the page automatically proceeds to Step 2.
2. Environment initialization
In the , go to Environment Initialization.
Configuration item | Configuration | Description |
Experience configuration information | None | Displays the architecture type, region, VPC, and other information configured in Step 1. |
Required resources | None | Displays the cloud resources that will be automatically created in Step 2. |
Resource distribution diagram | None | Displays the distribution of resources. |
Login information for the automatically created ECS instance
Name | Description |
ECS server name | MSHA_Quick_Start_ECS |
Logon username | root |
Logon password | MshaQuick123! |
Login information for the automatically created MySQL database
Name | Description |
Database name | quickstart |
Logon username | msha |
Logon password | Admin123 |
Click One-click Creation to automatically create the resources. After all resources in the list are created, click Next to proceed to Step 3.
If a resource fails to be created, check the error message. After you resolve the issue, click Retry to try again.
If the selected region has insufficient resources for the required specifications, click Cancel. The process automatically proceeds to Step 5. Wait for the resources to be released, finish the Quick Start, and then start over by selecting a new region.
If you click 'Cancel', the process automatically proceeds to Step 5 and releases the automatically created resources. Resources that you provided using 'Select existing...' are not released. After the release is complete, click 'Finish' to clear the data from this session. You can then start a new session.
All resources created by the Quick Start are private network resources.
Do not delete the created resources before completing Step 5 to prevent failures.
3. Multi-active instance
In the , go to Multi-active Instance.
Configuration item | Architecture type | Configuration |
Create business LDC |
| This creates the business LDC for the Quick Start. |
Create cloud-native gateway cluster |
| This creates the cloud-native gateway cluster for the Quick Start and associates it with the MSE cloud-native gateway created in Step 3. For more information, see Manage cloud-native gateway ingress clusters. Note If you did not check "Ingress layer component", this step is not executed. |
Create multi-active instance |
| This creates the Quick Start multi-active instance. |
Configure routing |
| This completes the global routing configuration for the Quick Start multi-active instance. After the configuration is complete, you can go to the MSE registry and configuration center to view the pushed configuration information. |
Apply baseline |
| This applies the baseline for the Quick Start multi-active instance. |
Configure ingress layer |
| This completes the ingress layer configuration for the Quick Start multi-active instance and sends the URI information. After the configuration is complete, you can view the routing information on the MSE instance. Note If you did not check "Ingress layer component", this step is not executed. |
Configure data layer |
| This completes the data layer configuration for the Quick Start multi-active instance. The data source is a self-managed MySQL database deployed on the ECS instance created in Step 3. The sync link is a two-way synchronization link. After the configuration is complete, you can go to the Data Transmission Service (DTS) console to view the sync task information. Note The synchronization link takes about 10 minutes to establish. Please wait. |
After the 'Create multi-active instance' step is complete, the Architecture Diagram on the right shows the architecture and monitoring data of the current instance. Because the application is not yet started, no monitoring data is available.
Click One-click Creation to automatically create the configurations for the multi-active instance. After all items in the list are complete, click Next to proceed to Step 4.
If a configuration fails to be created, check the error message. After you resolve the issue, click Retry to try creating the configuration again.
If the issue cannot be resolved, click Cancel. The process automatically proceeds to Step 5. Wait for the resources to be released, finish the Quick Start, and then start over.
4. Application startup
In the , go to Application Startup.
If you did not select the 'Ingress layer component' checkbox, this step is skipped.
Configuration item | Configuration | Description |
Confirm application startup | None | This section shows the changes required for startup parameters and configuration items after an application is connected to MSHA. |
Application startup | Click 'Confirm Startup' | This starts the demo application on the ECS instance. After the application starts completely, you can view monitoring information in the 'Architecture Diagram' on the right. Note If you did not select the 'Ingress layer component' checkbox, this step is skipped. Important The application takes 3 to 5 minutes to start. You can view monitoring information only after it has started completely. About 5 minutes after the application starts, you can view the service status and service monitoring in the MSE cloud-native gateway. A polling script starts with the application. This script generates traffic even if you do not call any interfaces. |
Call an interface to view traffic flow | Click 'Call Interface' and send a request in the pop-up window | This sends an HTTP request to the demo application. The routing tag for this request is fixed. |
Send a request to view the trace | Switch to the 'Application Graph' in the architecture diagram on the right and click the refresh button. | This lets you view the trace path. Each time you click the refresh button, the path of the most recent request is displayed. |
After you complete all steps, click Next to proceed to Step 5.
5. Application multi-active
In the , go to Application Multi-active.
Configuration item | Configuration | Description |
Automatic traffic switch | Click "Switch Traffic" | This takes you to the traffic switch ticket creation page, where you can switch traffic to other units and observe the changes in traces and monitoring metrics. |
Call an interface to view traffic flow | Click "Call Interface" and send a request in the pop-up window. Switch to the "Application Graph" in the architecture diagram on the right and click the refresh button. | This sends an HTTP request to the demo application. The routing tag for this request is fixed. View the latest trace information in the "Application Graph". Note If you did not check "Ingress layer component", the application does not start, and this call fails. |
Finish Quick Start | Click "Confirm Release" | You have completed the Quick Start. This step releases the automatically created multi-active instances, configurations, and cloud resources. Warning If you used an automatically created VPC and experienced the data layer component, you must manually release the security group created by DTS in the VPC after the synchronization link is released. The security group name is SG-DTS-GROUP-xxx. Otherwise, the VPC and peering connection instances cannot be automatically released. You can delete the DTS security group after the MSE registry and configuration center is released but before the MSE cloud-native gateway release begins. Releasing the MSE cloud-native gateway takes about 5 minutes. Important Resources that you added using "Select existing..." are not automatically released. Their status remains "To be released", which does not affect subsequent operations. Even if a resource fails to be released, clicking "Finish" still clears all Quick Start configurations. You must manually release any unreleased resources to avoid unnecessary charges. |
Click Finish to complete the Quick Start.
Before you start another Quick Start session, ensure that the multi-active instance and its configurations from the current session have been released. If not, release them manually.
FAQ
How do I troubleshoot an application startup failure?
1. In the , go to Cloud Assistant > Command Execution Results. Check the result of the "installDemoApp" command to confirm that it was successful. For more information, see View the execution result of a Cloud Assistant command and fix common issues.
2. If the command is successful, go to the > Instances page. Log on to the ECS server "MSHA_Quick_Start_ECS" and view the application logs. Then, run the following command to check port health:
netstat -tunlpIf the application starts normally, the following ports are in use:
Port | Description |
8080 | frontend service |
9001 | cart service |
9002 | product service |
9003 | trace service |
3306 | MySQL database |
If an application did not start normally, view its logs to identify the cause of the failure.
Log path | Description |
/home/admin/quickstart/app/frontend/frontend.out | frontend service log |
/home/admin/quickstart/app/cartservice/cartservice.out | cart service log |
/home/admin/quickstart/app/productservice/productservice.out | product service log |
/home/admin/quickstart/app/traceservice/traceservice.out | trace service log |
How do I troubleshoot a MySQL startup failure?
1. In the , go to Cloud Assistant > Command Execution Results. Check the result of the installMySQL command to confirm that it was successful. For more information, see View Cloud Assistant command execution results and fix common issues.