Open source core version | MSE-optimized version | Description |
2.3.2 | 2.3.2.1 | Lets you dynamically modify the number of namespaces based on the quota limit. The namespace quota limit can be dynamically adjusted in Quota Center. Supports local disaster recovery for authentication after RAM authentication is enabled. This prevents Nacos access from being affected by RAM system jitter. Fixes an issue where a service instance on a down ECS instance or pod may be slow to be removed from Nacos if the number of cluster connections exceeds the recommended value. Fixes a rare data inconsistency issue between nodes when a Nacos 1.X client is used. Fixes an issue where the size of a single configuration in configuration management cannot be dynamically changed based on the quota in Quota Center. Fixes an issue where a "file not found" error is prompted when you import a configuration. Fixes an issue where incorrect error codes are returned for some requests. Fixes an issue where gRPC TPS and QPS statistics are counted repeatedly. Fixes an issue where Eureka is incompatible with older client versions. Fixes an issue where a configuration cannot be obtained from configuration management when the default namespace is used and the configuration's namespace ID is set to public. Fixes an issue where data cannot be obtained when you use OpenAPI to get the service list from the registry if the page size is too large. Fixes an issue where a 403 error is returned when you access the client's healthCheck API.
|
2.3.2.0 | Supports Aliyun RAM V4 signatures. Supports the ActionTrail feature. For more information, see What is ActionTrail? Synchronizes with the code of open source version 2.3.2. Lets you adjust the retention period of the configuration history as needed. Supports recording operator information when a configuration is changed. Optimizes performance, including the gRPC push capability for service discovery and the login API performance. The core capabilities are more than twice as fast as open source self-managed Nacos. Enhances the throttling capability for internal APIs. Optimizes the logic for tag-based canary releases and supports configuring an upper limit on the number of canary release versions. Optimizes the configuration listening link to resolve frequent query issues. Fixes and improves some potential security risks. The Prometheus SD API supports RAM authentication. Optimizes the startup logic of the Eureka module to provide read services after data synchronization is complete.
|
2.2.3 | 2.2.3.3 | Supports tag-based canary release for configurations. Optimizes the data push logic to reduce the impact of a push failure on a single connection on the data push latency of other connections. Increases the default length limit of service provider metadata to 4096 characters. Fixes an issue where the cluster CPU usage spikes because some Nacos 2.x clients frequently call the login API. Fixes a namespace capacity display issue. Fixes a service registration failure issue caused by an excessively short heartbeat interval configured in Eureka.
|
2.2.3.1 | Disables the open source console by default. Supports the RAM AK whitelist feature. Supports the Eureka incremental data protocol. Optimizes the verification logic for engine upgrades or restarts. This supports non-disruptive engine changes and improves stability during engine upgrades or restarts. Optimizes the logic for obtaining source IP addresses to improve accuracy. Optimizes the cluster throttling capability to support more throttling features and improve engine stability. Optimizes the request parameter verification logic to clarify parameter error content. Significantly improves the performance of the Eureka module compared with previous versions. Fixes an issue where clients of a version later than 2.2 cannot receive an empty service list when forced empty list protection is disabled. Fixes an issue where the number of service providers is incorrectly counted when many services are registered in batches and concurrently. Fixes an issue where the configuration count limit in version 2.2.3.0 is invalid. Fixes an issue where data is not pushed when a single connection of the xDS protocol or MCP has a problem.
|
2.2.3.0 | Synchronizes with the kernel of open source version 2.2.3, including the change that the open source console logon page is not displayed when authentication is disabled. Lets you view the services registered, services subscribed to, and configurations listened to by risky client versions. Optimizes authentication-related prompts in the open source console. Optimizes the monitoring logic for push success rates. This ignores expected empty list protection triggers and prevents a drop in the push success rate when empty list protection is triggered.
|
2.1.2 | 2.1.2.2 | Optimizes the cleanup logic for expired metadata in the registry. This promptly cleans up metadata that is modified when a service instance does not exist. Reduces the time spent in intermediate states and with data inconsistency by optimizing the automatic switchover of running modes and the speed of automatic double-write stopping. Supports the underscore (_) character in the clusterName of the registry. Fixes an issue where the push track cannot be viewed after data is successfully pushed to the nacos-go-sdk. Fixes a rare issue where data cannot be queried when a client disconnects and registers a service at the same time. Fixes an issue where a 403 permission error is prompted for the client's configuration listener when authentication resources are configured at the dataId level.
|
2.1.2.1 | Lets Java applications that use service administration use Nacos service registration and discovery features without modifying code. Supports data communication encryption between the Nacos server-side and client.
|
2.1.2.0 | |
2.1.0 | 2.1.0.2 | Optimizes the empty list protection logic and narrows its trigger scope. Empty list protection is triggered only when necessary. Fixes an issue where the status code returned by the engine OpenAPI is always 500. Fixes an issue where horizontal notifications and Distro notifications fail during scale-in. Fixes an issue where the configuration obtained by the Cipher-256 algorithm is ciphertext when a 2.x client reads an encrypted configuration. Fixes a rare issue where incorrect data is published when pushing to Istio. Fixes an issue where garbled characters appear in Chinese configurations obtained using the ACM-Node.js-SDK.
|
2.1.0.1 | Optimizes the empty list protection judgment for Dubbo multi-subscription scenarios. This prevents the client from printing many invalid empty list protection logs. Optimizes the push task model for greater stability during large-scale pushes. Fixes an issue where the client frequently prints out-date logs.
|
2.1.0.0 | Supports the empty list protection feature to improve high availability (HA). This feature is available only in the Professional Edition. For more information, see Empty list protection. Optimizes the long polling capability for configuration listening, improving performance by about 100%.
|
2.0.4 | 2.0.4.0 | Supports Dragonwell for improved performance. This feature is available only in the Professional Edition. Supports registry authentication. Supports the RAM control policy feature. Fixes an issue where connections between nodes may disconnect and not reconnect during concurrent startup. Fixes an issue where the encryption algorithm may be incorrect when you import an encrypted configuration.
|
2.0.3 | 2.0.3.2 | |
2.0.3.1 | Improves compatibility with the ACM protocol. This supports ACM clients and allows configuration operations using the ACM protocol. Fixes an issue where the time in the configuration history is inaccurate after a configuration is modified. Fixes an issue where entering {address}:8848/nacos in the open source console fails to redirect to the console interface. Fixes an issue where garbled characters appear when you publish Chinese configurations in the open source console. Fixes an issue where the number of service providers is incorrect because the Go SDK fails the initial pull and does not retry, or the retry status is abnormal. Fixes an issue where the Eureka protocol frequently prints logs. Fixes an issue where garbled characters appear when you publish Chinese configurations using the nacos-nodejs-sdk. Improves support for the address server mode in MSE Nacos and fixes an issue where the address server does not work in standalone mode.
|
2.0.3.0 | Is compatible with the ACM (Diamond) protocol. This allows ACM users to seamlessly migrate to this version. Improves the stability of importing and exporting encrypted configurations. Lets you export configurations from ACM products and import them into the configuration management service of MSE Nacos.
|
2.0.1 | 2.0.1.1 | Optimizes the database query logic to reduce the impact of database jitter on server performance. Fixes a frontend display issue where all instances appear to change together when an instance is brought online or offline, or its weight is changed in the console. Fixes an issue where metadata is not deleted after expiration when an instance goes offline while using a Nacos 1.x client. Fixes an issue where Istio (cloud-native gateway) cannot detect changes when an instance goes offline or its weight is changed.
|
2.0.1.0 | Extends client compatibility to Java Client 0.8. Optimizes the performance of the MCP and xDS protocols. Improves the stability of service data push. Fixes an issue where the namespace page displays an incorrect maximum configuration value. Fixes an issue where new nodes may fail to join the cluster during scale-out.
|
2.0.0 | 2.0.0.0 | Supports gRPC-based Nacos registry and configuration management features. Improves performance by about 10 times compared with the Basic Edition. Supports a more complete authentication, encryption, and decryption system.
|