Microservices Engine:Nacos engine version

3.1.1 / 3.1.1.1

QPS throttling for the Eureka full query API and Eureka compatibility fixes.

Feature

• [Eureka] QPS throttling for the Eureka full query API /apps.

Bug fix

• [Eureka] Fixed an issue where the statusUpdate API may cause many calls to the full query API /apps.

• [Eureka] Fixed a content-type issue with the XML response when a Eureka heartbeat fails with a 404 error.

• [Eureka] Fixed an issue where a lowercase instance ID may cause glitches in the call volume of the full query API /apps.

• [MCP] Fixed an MCP Server cache inconsistency issue.

3.1.1 / 3.1.1.0

Synchronized with open source version 3.1.1. Added AI Guardrails support for MCP service definitions.

Feature

• Synchronized with open source version 3.1.1.

• [MCP] AI Guardrails support when updating MCP service definitions.

Bug fix

• [Auth] Fixed an issue where the source IP address of a request from a Nacos 2.X client over the public network is read as a private IP address when the AccessKey (AK) whitelist for authentication is enabled.

• [Eureka] Fixed an issue where some APIs remain accessible after the Eureka feature is disabled.

• Fixed an issue where incorrect return codes are returned for some requests that have invalid parameters.

3.1.0 / 3.1.0.0

Synchronized with open source version 3.1.0. Added A2A Registry support.

Feature

• Synchronized with open source version 3.1.0.

• [Registry] A2A Registry support. For more information, see Agent Management.

3.0.1 / 3.0.1.0

Synchronized with open source version 3.0.1. Added data source management, MCP registry, and default authentication for the open source console.

Feature

• Synchronized with open source version 3.0.1.

• [Config] Data source management to help automatically rotate the key information of the data source that an application accesses.

• [MCP] MCP registry to quickly convert existing APIs into MCP APIs.

• [Auth] Authentication enabled by default for the open source console and administrator password reset for the open source console.

2.3.2 / 2.3.2.1

Dynamic namespace quota management and local disaster recovery for RAM authentication. Multiple bug fixes across configuration management, the registry, and Eureka.

Feature

• [Config] Dynamic modification of the number of namespaces based on the quota limit. The namespace quota limit can be dynamically adjusted in Quota Center.

• [Auth] Local disaster recovery for authentication after RAM authentication is enabled. This prevents Nacos access from being affected by RAM system jitter.

Bug fix

• [Registry] Fixed 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.

• [Registry] Fixed a rare data inconsistency issue between nodes when a Nacos 1.X client is used.

• [Config] Fixed an issue where the size of a single configuration in configuration management cannot be dynamically changed based on the quota in Quota Center.

• [Config] Fixed an issue where a "file not found" error is prompted when you import a configuration.

• Fixed an issue where incorrect error codes are returned for some requests.

• Fixed an issue where gRPC TPS and QPS statistics are counted repeatedly.

• [Eureka] Fixed an issue where Eureka is incompatible with older client versions.

• [Config] Fixed 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.

• [Registry] Fixed 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.

• [Auth] Fixed an issue where a 403 error is returned when you access the client's healthCheck API.

2.3.2 / 2.3.2.0

Synchronized with open source version 2.3.2. Added RAM V4 signature support, ActionTrail integration, and performance improvements for gRPC push and login API.

Feature

• [Auth] Aliyun RAM V4 signature support.

• ActionTrail feature support. For more information, see What is ActionTrail?

• Synchronized with the code of open source version 2.3.2.

• [Config] Adjustable retention period of the configuration history.

• [Config] Operator information recording when a configuration is changed.

• [Auth] Prometheus SD API support for RAM authentication.

Enhancement

• Performance improvements including the gRPC push capability for service discovery and the login API performance. Core capabilities are more than twice as fast as open source self-managed Nacos.

• [Auth] Enhanced throttling capability for internal APIs.

• [Config] Optimized logic for tag-based canary releases with support for configuring an upper limit on the number of canary release versions.

• [Config] Optimized configuration listening link to resolve frequent query issues.

• [Eureka] Optimized startup logic of the Eureka module to provide read services after data synchronization is complete.

Security

• Fixed and improved some potential security risks.

2.2.3 / 2.2.3.3

Tag-based canary release for configurations and increased default metadata length limit.

Feature

• [Config] Tag-based canary release for configurations.

Enhancement

• [Registry] Optimized data push logic to reduce the impact of a push failure on a single connection on the data push latency of other connections.

• [Registry] Default length limit of service provider metadata increased to 4,096 characters.

Bug fix

• [Auth] Fixed an issue where the cluster CPU usage spikes because some Nacos 2.x clients frequently call the login API.

• Fixed a namespace capacity display issue.

• [Eureka] Fixed a service registration failure issue caused by an excessively short heartbeat interval configured in Eureka.

2.2.3 / 2.2.3.1

Open source console disabled by default. Added RAM AK whitelist and Eureka incremental data protocol support. Stability improvements for engine upgrades and restarts.

Feature

• Open source console disabled by default.

• [Auth] RAM AK whitelist feature support.

• [Eureka] Eureka incremental data protocol support.

Enhancement

• Optimized verification logic for engine upgrades or restarts. This supports non-disruptive engine changes and improves stability during engine upgrades or restarts.

• Optimized logic for obtaining source IP addresses to improve accuracy.

• Optimized cluster throttling capability to support more throttling features and improve engine stability.

• Optimized request parameter verification logic to clarify parameter error content.

• [Eureka] Significantly improved performance of the Eureka module compared with previous versions.

Bug fix

• Fixed an issue where clients of a version later than 2.2 cannot receive an empty service list when forced empty list protection is disabled.

• [Registry] Fixed an issue where the number of service providers is incorrectly counted when many services are registered in batches and concurrently.

• Fixed an issue where the configuration count limit in version 2.2.3.0 is invalid.

• Fixed an issue where data is not pushed when a single connection of the xDS protocol or MCP has a problem.

2.2.3 / 2.2.3.0

Synchronized with the kernel of open source version 2.2.3. Added risky client version visibility.

Feature

• Synchronized 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.

• Visibility into services registered, services subscribed to, and configurations listened to by risky client versions.

Enhancement

• [Auth] Optimized authentication-related prompts in the open source console.

• [Registry] Optimized 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

Optimized expired metadata cleanup and automatic mode switchover in the registry.

Enhancement

• [Registry] Optimized cleanup logic for expired metadata in the registry. This promptly cleans up metadata that is modified when a service instance does not exist.

• [Registry] Reduced 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.

• [Registry] Support for the underscore (_) character in the clusterName of the registry.

Bug fix

• Fixed an issue where the push track cannot be viewed after data is successfully pushed to the nacos-go-sdk.

• [Registry] Fixed a rare issue where data cannot be queried when a client disconnects and registers a service at the same time.

• [Auth] Fixed 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 / 2.1.2.1

Service administration integration for Java applications and data communication encryption.

Feature

• Java applications that use service administration can use Nacos service registration and discovery features without modifying code.

• [Auth] Data communication encryption between the Nacos server-side and client.

2.1.2 / 2.1.2.0

gzip compression for registry address push and anti-fragility capabilities.

Feature

• [Registry] gzip compression for pushing registry addresses.

• Anti-fragility capabilities:

  • Connection throttling.

  • TPS throttling for configuration publishing.

  • QPS throttling for configuration reading.

  • TPS throttling for service data push.

2.1.0 / 2.1.0.2

Optimized empty list protection and fixes for push and notification issues.

Enhancement

• [Registry] Optimized empty list protection logic and narrowed its trigger scope. Empty list protection is triggered only when necessary.

Bug fix

• Fixed an issue where the status code returned by the engine OpenAPI is always 500.

• Fixed an issue where horizontal notifications and Distro notifications fail during scale-in.

• [Config] Fixed an issue where the configuration obtained by the Cipher-256 algorithm is ciphertext when a 2.x client reads an encrypted configuration.

• [Registry] Fixed a rare issue where incorrect data is published when pushing to Istio.

• [Config] Fixed an issue where garbled characters appear in Chinese configurations obtained using the ACM-Node.js-SDK.

2.1.0 / 2.1.0.1

Stability improvements for empty list protection and large-scale push scenarios.

Enhancement

• [Registry] Optimized empty list protection judgment for Dubbo multi-subscription scenarios. This prevents the client from printing many invalid empty list protection logs.

• [Registry] Optimized push task model for greater stability during large-scale pushes.

Bug fix

• Fixed an issue where the client frequently prints out-date logs.

2.1.0 / 2.1.0.0

Empty list protection for high availability and doubled long polling performance.

Feature

• [Registry] 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.

Enhancement

• [Config] Optimized long polling capability for configuration listening, improving performance by about 100%.

2.0.4 / 2.0.4.0

Dragonwell support, registry authentication, and RAM control policy.

Feature

• Dragonwell support for improved performance. This feature is available only in the Professional Edition.

• [Auth] Registry authentication.

• [Auth] RAM control policy feature support.

Bug fix

• Fixed an issue where connections between nodes may disconnect and not reconnect during concurrent startup.

• [Config] Fixed an issue where the encryption algorithm may be incorrect when you import an encrypted configuration.

2.0.3 / 2.0.3.2

Bug fixes for address server initialization and configuration authentication.

Bug fix

• Fixed an occasional failure in address server initialization.

• [Auth] Fixed an issue where nodes remain in the recovering state after configuration authentication is enabled.

2.0.3 / 2.0.3.1

ACM protocol compatibility and fixes for console and SDK issues.

Feature

• Improved compatibility with the ACM protocol. This supports ACM clients and allows configuration operations using the ACM protocol.

Bug fix

• [Config] Fixed an issue where the time in the configuration history is inaccurate after a configuration is modified.

• Fixed an issue where entering {address}:8848/nacos in the open source console fails to redirect to the console interface.

• Fixed an issue where garbled characters appear when you publish Chinese configurations in the open source console.

• [Registry] Fixed 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.

• [Eureka] Fixed an issue where the Eureka protocol frequently prints logs.

• [Config] Fixed an issue where garbled characters appear when you publish Chinese configurations using the nacos-nodejs-sdk.

• Improved support for the address server mode in MSE Nacos and fixed an issue where the address server does not work in standalone mode.

2.0.3 / 2.0.3.0

ACM (Diamond) protocol compatibility for seamless migration from ACM.

Feature

• Compatible with the ACM (Diamond) protocol. This allows ACM users to seamlessly migrate to this version.

• [Config] Export configurations from ACM products and import them into the configuration management service of MSE Nacos.

Enhancement

• [Config] Improved stability of importing and exporting encrypted configurations.

2.0.1 / 2.0.1.1

Optimized database query performance and fixes for console and registry issues.

Enhancement

• Optimized database query logic to reduce the impact of database jitter on server performance.

Bug fix

• Fixed 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.

• [Registry] Fixed an issue where metadata is not deleted after expiration when an instance goes offline while using a Nacos 1.x client.

• [Registry] Fixed an issue where Istio (cloud-native gateway) cannot detect changes when an instance goes offline or its weight is changed.

2.0.1 / 2.0.1.0

Extended client compatibility and improved MCP and xDS protocol performance.

Feature

• Client compatibility extended to Java Client 0.8.

Enhancement

• Optimized performance of the MCP and xDS protocols.

• [Registry] Improved stability of service data push.

Bug fix

• Fixed an issue where the namespace page displays an incorrect maximum configuration value.

• Fixed an issue where new nodes may fail to join the cluster during scale-out.

2.0.0 / 2.0.0.0

gRPC-based Nacos registry and configuration management with approximately 10x performance improvement over the Basic Edition.

Feature

• [Registry] [Config] gRPC-based Nacos registry and configuration management features.

• [Auth] A more complete authentication, encryption, and decryption system.

Enhancement

• Performance improved by about 10 times compared with the Basic Edition.

1.2.1 / 1.2.1.3

Feature

• [Auth] RAM control policy feature support.

Enhancement

• Optimized running thread pool to support automatic dynamic adjustment.

Bug fix

• [Registry] Fixed an issue where some queries for service subscribers are inaccurate.

1.2.1 / 1.2.1.2

Enhancement

• Optimized database dependencies to reduce the impact of database pressure jitter on Nacos request responses.

Bug fix

• [Config] Fixed an issue where configurations exported from ACM cannot be imported.

1.2.1 / 1.2.1.1

Enhancement

• Optimized performance of the MCP and xDS protocols.

Bug fix

• Fixed an issue where the namespace page displays an incorrect maximum configuration value.

1.2.1 / 1.2.1.0

HTTP-based Nacos registry and configuration management features.

1.1.3 (Discontinued)

HTTP-based Nacos registry features.