Microservices Registry FAQ

FAQ

Why wasn't the 10% discount applied to my first subscription purchase of Microservices Engine (MSE)?

First-time customers receive a 10% discount. The discount is reflected in the final order. If you do not receive the discount, you can cancel the unpaid order and place a new one.

Which regions does MSE support?

For more information about the regions that MSE supports, see Available regions.

How to use MSE?

Microservices Engine (MSE) is a one-stop microservices platform for mainstream open source microservices frameworks such as Spring Cloud and Dubbo. MSE provides microservices governance, a microservices registry, and a managed configuration center. To learn how to use MSE, see the MSE Learning Path.

Does MSE support public network access for development and testing?

This is supported.

Does MSE support auto-renewal?

MSE supports the auto-renewal feature. You can set this feature in the MSE console under Fees > Renewal Management.

Managed cluster issues

Are the ZooKeeper, Nacos, and Eureka instances provided by MSE hosted clusters dedicated and independent?

Yes, they are. MSE provides a dedicated instance for each user. Each instance is physically isolated and cannot be shared with other users.

Are ZooKeeper instances from MSE-hosted clusters identical to the open source version?

MSE-managed ZooKeeper instances are the same as Apache ZooKeeper instances in terms of API usage and version compatibility. You can use them without modifying your application code. Additionally, MSE has modified and optimized these instances for high performance and high availability. These modifications and optimizations do not affect how you use the instances.

When does a Nacos cluster support configuration management?

MSE now supports the Nacos configuration management feature. For more information, see Create a configuration.

Can you scale, upgrade, or downgrade MSE?

Yes, you can. For more information, see Change instance specifications and Upgrade the Nacos engine version.

How to use Nacos namespaces in MSE?

After you create a namespace, add the namespace ID to your application's configuration. When the service registers, it is automatically placed in the corresponding namespace.

Configuration code:

After you create a namespace, add the namespace ID to your application configuration. When a service is registered, it is associated with that namespace.

Configure the code

• Spring Cloud: spring.cloud.nacos.discovery.namespace=5cbb70a5-88b8-4fd9-84c1-d43479ae****

• Dubbo:

  • Properties: dubbo.registry.parameters.namespace=5cbb70a5-88b8-4fd9-84c1-d43479ae****

  • XML: <dubbo:registry address="nacos://mse-f1abb3b0-p.nacos-ans.mse.aliyuncs.com:8848?namespace=5cbb70a5-88b8-4fd9-84c1-d43479ae****"/>

Can clusters from the public preview period be directly upgraded to a monthly subscription, or must they be repurchased?

Yes, you can change the billing method from pay-as-you-go to subscription. For more information, see Change a billing method from pay-as-you-go to subscription.

Should I use private or public IP addresses for a whitelist?

IP address whitelists are used to control access from the public network, so they must contain public IP addresses. Whitelists do not block access from private networks.

Instance issues

Why does the created ZooKeeper/Nacos/Eureka instance not have a public IP address?

If you purchase an instance without selecting public bandwidth, the instance is not assigned a public IP address. By default, the public bandwidth is 0 Mbit/s. You can increase the public bandwidth by changing the instance specifications. For more information, see Change instance specifications.

Will upgrading an MSE Nacos instance affect normal services?

For multi-instance clusters, the upgrade does not affect your services. During the upgrade process, servers are restarted in sequence. This ensures that Nacos services are not interrupted and that nodes are gracefully started and shut down. For single-instance clusters, the restart may interrupt your services. We recommend that you use a cluster with three or more nodes in a production environment.

How many Nacos nodes are recommended for a production environment?

We recommend that you determine the number of nodes using the following formula: Number of nodes = 2n + 1, where n is an integer. The optimal number of nodes depends on your actual usage.

Does MSE Nacos support the open source Nacos console?

MSE currently supports only Nacos version 1.2.1. You can use the public address :8848/nacos to access the Nacos open source console. For other instance types, you must use the corresponding client SDK to access their public addresses.

Why is there no configuration center in my Nacos-based MSE instance?

The configuration management feature is supported by MSE Nacos 1.2.1, but not by version 1.1.3. You can upgrade your instance to version 1.2.1 to use this feature. For more information, see Upgrade Nacos engine version.

What are the Nacos Client version requirements and the recommended version for MSE?

We recommend that you use Nacos client 1.4.2. This client version resolves compatibility issues.

Does MSE Nacos have an OpenAPI?

Yes, it does. For more information, see the OpenAPI Guide.

Why can I only create and edit an MSE Nacos namespace, but not delete it?

MSE Nacos version 1.1.3 does not support namespace deletion. You can upgrade to version 1.2.1, which supports this feature. For more information, see Upgrade Nacos engine version.

How to take a Nacos service offline in MSE?

You can use the /nacos/v1/ns/instance PUT API of the Nacos OpenAPI and set the enable parameter to false to take a service offline. For more information, see the OpenAPI Guide.

If an MSE instance is deleted, can it be recovered? If so, how long does the recovery take?

No. Once an MSE instance is deleted, it cannot be recovered. For subscription instances, you will receive a text message reminder seven days before your instance expires.

If you create multiple instances in MSE, can services call each other?

When you create an MSE instance, you must associate it with a VPC. The instance can only be accessed by other resources within the same VPC. Therefore, services can call each other only if their instances are in the same VPC or in interconnected VPCs.

What should I do if I purchased the wrong MSE instance type?

If your instance is a pay-as-you-go instance, you can release the instance. If your instance is a subscription instance, you can unsubscribe from the instance and apply for a refund.

Configuration issues

Does MSE monitoring support Prometheus dynamically reading the service list from Nacos to retrieve metrics?

Yes, it is supported, but not displayed in MSE.

What is the difference between MSE and ACM?

Application Configuration Management (ACM) is a separate Alibaba Cloud service that provides a shared configuration center intended for developers. In contrast, MSE Nacos can communicate with open source products, offers dedicated instances, and provides better performance, security protection, and availability that is guaranteed by a Service-Level Agreement (SLA). This makes MSE Nacos more suitable for production environments.

Is the configuration center of MSE Nacos 1.2.1 compatible with ACM? Can data be migrated between them?

Yes, they are compatible. You can export the configurations from ACM. Then, use the MSE Nacos public network address :8080/nacos to access the open source console and import the configurations into Nacos. For more information about how to enable public network access for an MSE instance, see Set a whitelist.

Can I grant only write permission for a specific MSE instance?

You must grant the RAM user read permission on all instances and read and write permission on a specific instance. To do this, you can combine the policy examples provided in the documentation for using MSE as a RAM user. For more information, see Grant permissions on a registry and configuration center.

{
  "Version": "1",
  "Statement": [
    {
      "Action": [
        "mse:*"
      ],
      "Resource": "acs:mse:*:*:instance/mse-cn-0pp1j8om80a",
      "Effect": "Allow"
    },
    {
      "Action": [
        "mse:List*",
        "mse:Query*",
        "mse:Get*"
      ],
      "Resource": "acs:mse:*:*:*",
      "Effect": "Allow"
    }
  ]
}

How to use a managed service for Consul with a Spring Cloud application on the cloud?

You can use the cloud-consul tool to synchronize services to MSE, and then change the registry in your code to the MSE registry.

What should I do if a Dubbo service deployed in EDAS still registers with the built-in EDAS registry even though it is configured to use MSE as the registry and ACM as the configuration center?

Add the following two parameters and then restart or redeploy your application to make the change take effect.

• -Dnacos.use.endpoint.parsing.rule=false

• -Dnacos.use.cloud.namespace.parsing=false