This topic provides answers to some frequently asked questions about Microservices Registry of Microservices Engine (MSE). Before you use MSE, you must be familiar with this topic to check whether MSE meets your requirements.
Common issues
Why have I not received a 10% discount when I purchase a subscription MSE instance for the first time?
If you purchase MSE that uses the subscription billing method for the first time, you can receive a 10% discount. The actual amount of the bill that is generated by your first MSE order is determined by the system. If you do not receive a 10% discount for your first purchase, you can cancel the unpaid order and place another order to enjoy a 10% discount.
Which regions are supported by MSE?
For more information about the regions supported by MSE, see Supported regions.
How do I use MSE?
MSE is a one-stop microservices platform designed for the two mainstream open source microservices frameworks, Spring Cloud and Dubbo. MSE provides three modules: Microservices Governance, Microservices Registry, and Cloud-native Gateway. Microservices Registry provides managed instances, and Cloud-native Gateway provides managed gateways. For more information about how to use MSE, go to the learning path of MSE.
Does MSE support Internet access to facilitate development and testing?
Yes, MSE supports Internet access to facilitate development and testing.
Does MSE support auto-renewal?
Yes, MSE supports auto-renewal. You can log on to the MSE console and choose Expenses > Renewal Management in the top navigation bar to configure auto-renewal for MSE instances.
Instance management issues
Are MSE-managed ZooKeeper, Nacos, and Eureka instances dedicated instances?
Yes, MSE-managed ZooKeeper, Nacos, and Eureka instances are dedicated instances. MSE provides a dedicated instance for each user. These instances are physically isolated and cannot be shared among users.
Are MSE-managed ZooKeeper instances the same as Apache ZooKeeper instances?
Yes, MSE-managed ZooKeeper instances are the same as Apache ZooKeeper instances in terms of API usage and version compatibility. You can use MSE-managed ZooKeeper instances without the need to modify application code. MSE-managed ZooKeeper instances are modified and optimized for high performance and high availability. These modifications and optimizations do not affect your use.
Do Nacos instances support configuration management?
Yes, Nacos instances support configuration management. For more information, see Create a configuration.
Can I perform scaling for MSE instances or change the specifications of MSE instances?
Yes, you can perform scaling for MSE instances or change the specifications of MSE instances. For more information, see Change instance specifications and Upgrade a Nacos version.
How do I use the namespaces of MSE Nacos instances?
After you create a namespace for an MSE Nacos instance, you can add the namespace ID to the configuration of your application. When your application is registered with the MSE Nacos instance, the namespace ID appears on the Namespace page in the MSE console.
Sample configuration
Sample configuration of a Spring Cloud application:
spring.cloud.nacos.discovery.namespace=5cbb70a5-88b8-4fd9-84c1-d43479ae****Sample configuration of a Dubbo application:
.properties file:
dubbo.registry.parameters.namespace=5cbb70a5-88b8-4fd9-84c1-d43479ae****XML file:
<dubbo:registry address="nacos://mse-f1abb3b0-p.nacos-ans.mse.aliyuncs.com:8848?namespace=5cbb70a5-88b8-4fd9-84c1-d43479ae****"/>
Can I change my pay-as-you-go instances that are created during the public preview period to subscription instances, or do I need to create subscription instances?
Yes, you can change your pay-as-you-go instances that are created during the public preview period to subscription instances. For more information, see Change the billing method of an MSE instance from pay-as-you-go to subscription.
Can I add private IP addresses or public IP addresses to an IP address whitelist?
IP address whitelists are used for Internet access control. Therefore, you must add public IP addresses to the whitelists. Whitelists do not block access from private networks.
Instance issues
Why does my ZooKeeper, Nacos, or Eureka instance not have a public IP address?
When you create the ZooKeeper, Nacos, or Eureka instance, you do not specify the public bandwidth for the instance, and the default public bandwidth value 0 Mbit/s is used. Therefore, your instance does not have a public IP address. To address this issue, you can specify a non-zero value for the public bandwidth of the instance. For more information, see Change instance specifications.
Are my services affected during the upgrade of an MSE Nacos instance?
For multi-instance clusters, the restart does not affect your services. During the instance upgrade process, servers are restarted in sequence. This ensures that Nacos services are not interrupted during the upgrade and nodes are gracefully started and shut down during the restart. For single-instance clusters, the restart may cause your services to be interrupted. We recommend that you use a cluster with more than three nodes in the online production environment.
How many nodes do I need to specify for my Nacos instance in the production environment?
We recommend that you determine the number of nodes by using the following formula: Number of nodes = 2 × n + 1. n indicates a random integer. The optimal number is determined based on actual usage.
Is the open source Nacos console supported by MSE Nacos?
The open source Nacos console is supported only by MSE Nacos 1.2.1. If your Nacos instance runs on MSE Nacos 1.2.1, you can use a public endpoint in the <Public IP address>:8848/nacos format to access the open source Nacos console. If your instance runs on another MSE Nacos version, you must use the required client SDK to access the console.
I have purchased an MSE Nacos instance, why am I unable to use features related to configuration centers?
The features related to configuration centers are supported by MSE Nacos 1.2.1, but not by 1.1.3. You can upgrade your MSE Nacos instance to 1.2.1. For more information, see Upgrade a Nacos version.
Which Nacos client version is recommended for use in MSE?
We recommend that you use the client that corresponds to MSE Nacos 1.4.2. Compatibility issues are resolved in the client.
Does MSE Nacos support API operations?
Yes, your MSE Nacos instance supports API operations. For more information, visit OpenAPI Guide.
In addition to creating or editing namespaces, can I delete namespaces from MSE Nacos instances?
Namespace deletion is supported by MSE Nacos 1.2.1, but not by 1.1.3. You can upgrade your instance to 1.2.1. For more information, see Upgrade a Nacos version.
How do I shut down the MSE Nacos instance?
Use the /nacos/v1/ns/instance PUT operation of Nacos API operations and set enable to false to shut down the MSE Nacos instance. For more information, visit OpenAPI Guide.
After an instance is shut down, consumer applications cannot run on the instance.
Does Alibaba Cloud provide solutions to restore a deleted MSE instance? If yes, how long does it take to restore the instance?
A text message is sent to you seven days before your instance expires. If your instance is deleted, the instance cannot be restored.
Is service interoperability supported if I have multiple MSE instances?
When you create an MSE instance, you must select a VPC ID for the instance. The created instance can only be assessed by other instances that reside in the same VPC. If instances in multiple VPCs can access each other, service interoperability among instances across the VPCs is supported.
If I have created an MSE instance whose type is not what I want, how do I release or unsubscribe from the instance and create another instance?
If your instance is a pay-as-you-go instance, release the instance. If your instance is a subscription instance, unsubscribe from the instance and apply for a refund.
Configuration issues
Can MSE use Managed Service for Prometheus to dynamically read service lists of Nacos instances to collect metric data?
Yes, MSE can use Managed Service for Prometheus to read service lists of Nacos instances to collect metric data. However, the collected metric data cannot be displayed in the MSE console.
What is the difference between MSE and Application Configuration Management?
Application Configuration Management is a separate Alibaba Cloud service. It is a shared configuration center that is intended for developers. MSE Nacos can communicate with open source products, offers dedicated services, and provides better performance, SLA-guaranteed availability, and security protection. MSE Nacos is more suitable for use in the production environment.
Is the configuration center provided by MSE Nacos 1.2.1 compatible with Application Configuration Management? Can configurations be migrated between MSE Nacos 1.2.1 and Application Configuration Management?
Yes, the configuration center provided by MSE Nacos 1.2.1 is compatible with Application Configuration Management. You can export configurations from Application Configuration Management, use the public endpoint of an MSE Nacos instance to access the open source Nacos console, and then import the configurations to the MSE Nacos instance. The public endpoint is in the <Public IP address>:8080/nacos format For more information about how to enable Internet access to MSE, see Configure an IP address whitelist.
Can I grant my RAM user only the write permissions on a single MSE instance?
No, you cannot grant your RAM user only the write permissions on a single MSE instance. You must grant your RAM user the read permissions on all MSE instances that belong to your account or both the read and write permissions on a single MSE instance. For more information, see the "Example 1" and "Example 2" sections in "Grant permissions on Microservices Registry resources." You must enter the code in both the "Example 1" and "Example 2" sections. For more information, see Grant permissions on Microservices Registry resources.
{
"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 do I use an MSE instance to manage my Spring Cloud application that is registered with a Consul registry?
You can use the cloud-consul tool to synchronize the data of your application to the MSE instance and replace the registry address in your code with the address of the MSE instance. For more information about the cloud-consul tool, visit nacos-sync-example/cloud-consul/.
My Dubbo application that is deployed in Enterprise Distributed Application Service (EDAS) uses an MSE instance as a registry and Application Configuration Management as a configuration center. After my Dubbo application starts, the application is still registered with a self-managed registry of EDAS. What do I do?
Add the following parameter settings 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