Documentation

FAQ

Nacos standard questions

What is Nacos

Nacos dedicated to help you find, micro configuration and management services. Nacos provides a set of simple and easy to use feature set, help you quickly realize dynamic service discovery, service configuration, service metadata, and traffic management. Details you can refer to Nacos website.

Nacos how to support more than the environment

In daily use are often need different environment, such as daily, pretest, online environment, if it is a logical isolation, can use the namespace Nacos support namespace to support more environmental isolation, can create multiple namespaces in Nacos console. If you need physical isolation, will deploy more sets of Nacos environment.

Nacos whether production is available

Nacos in January 2019 issued a Pre - GA version, to support the security isolation, monitoring and service migration on the last mile of production, in a more stable support the user's production environment. Details you can refer to Nacos release v0.8.0 Pre - GA version, the safe and stable production.

Nacos version plan

Nacos 0.8.0 to support production available, version 1.0 to mass production is available, version 2.0 plan and K8s, Spring Cloud, and further integration Service Mesh, Serverless, details you can refer to Nacos roadmap.

Nacos dependent

In stand-alone mode, Nacos without any rely on, in cluster mode, Nacos rely on Mysql storage, details you can refer to Nacos deployment.

Nacos using open source licenses

Nacos using Apache 2.0.

Nacos operational questions

Nacos standalone deployment

You can refer to the manual Nacos website deployment quick start.

Nacos standalone deployment using Mysql

Nacos stand-alone mode defaults to using the embedded database as the storage engine, if you want to change your mysql installation, you can refer to website document.

Nacos production deployment

Production environment using Nacos in order to achieve high availability cannot use stand-alone mode, need to build Nacos cluster, specific details can refer to the manual cluster deployment.

Nacos Docker deployment

In addition to using compressed package deployment Nacos, Nacos also provides a corresponding Docker image, when Nacos release new versions, Nacos will release the corresponding image version supports Docker deployment.Specific details you can refer to Nacos Docker.

How to deploy in k8s Nacos

In production deployment Nacos cluster, if for Nacos expansion operation, need to manually change the cluster IP file, start a new Nacos service.In order to automate operations, k8s Nacos and combined use of StatefulSets provides automatic operations plan, to dynamic scalability Nacos capacity, specific details reference Kubernetes Nacos.

How to monitor Nacos

Nacos0.8 version provides the Metrics data exposed ability, can pass the Metrics data to monitor the running status of Nacos, the content of the details you can refer to Nacos monitor.

Nacos used questions

Zookeeper service can be migrated to Nacos?

Can through the Nacos - Sync moved the Zookeeper service and Nacos, can also be migrated from Nacos Zookeeper, specific details can be used as Nacos Sync reference.

Nacos support multiple configuration files

Nacos through Spring Cloud Alibaba Nacos Config support multiple configuration files, configuration can be stored in a separate configuration file.The associated issue, details refer to the document Spring Cloud Alibaba Nacos Config.

Nacos support Dubbo

Nacos version 0.6 and Dubbo integration, support the use of Nacos as registry, related issue, details refer to the document Nacos and Dubbo fusion become registry.

Nacos support Spring system

Nacos perfect supports the Sping technology stack, details refer to the document Nacos SpringNacos Spring BootSpring Cloud.

Don't use Nacos SDK how to access the Nacos

Nacos network interaction is implemented based on Http protocol, provides the Open-API can easily achieve Nacos access.

Nacos support for multiple languages

Nacos currently only supports Java, support for other languages are being developed, also need your support to build together.

Nacos 0.8 version logon failure

Nacos version 0.8 when using its and no JAVA_HOME environment variable, Nacos can launch successful, because yum install installed its the Java command to register a beneath /bin directory, and so can cause abnormal SignatureException.This problem has been repair, version 0.9 release, the specific details can refer to the issue.

Server error java.lang.IllegalStateException: unable to find local peer: 127.0.0.1:8848

This problem because Nacos get native IP, don't get to the correct external IP. The need to guarantee the InetAddress.getLocalHost().getHostAddress() or the result of the hostname -i was with the cluster. The conf configuration of IP is the same.

Nacos configuration for encryption

Nacos plan in 1.X version's ability to provide encryption, currently does not support encryption, can only rely on the SDK prepared encryption endures Nacos again.

Nacos at 401 error

Nacos server error, check the server logs, refer to the issue.

Nacos weight not to take effect

Nacos console editors weights, at present from SpringCloud client and Dubbo client didn't get through, so can't take effect. For SpringCloud client application can realize the load balancer Ribbon for weighting filter.

Nacos how to enlarge shrinks capacity

Currently supported modify the cluster.conf file in a way that expanding capacity, after the change without restart, the Server will automatically refresh the new content to the file.

Nacos client modify the log level

Configuration - D parameters com.alibaba.nacos.naming.log.level set naming the client log level, such as setting for the error:-Dcom.alibaba.nacos.naming.log.level=error Similarly, - D parameters com.alibaba.nacos.config.log.level is used to set the config client log level.

Nacos and Zipkin integration Service not found error

Configuration spring-cloud-seluth parameters: spring.zipkin.discovery-client-enabled=false.

If there is still a Service not found error, is recommended to use the open-api will Zipkin-server instance is registered as a permanent Service:

curl -X POST 'http://127.0.0.1:8848/nacos/v1/ns/instance?port=9411&healthy=true&ip=127.0.0.1&weight=1.0&serviceName=zipkin-server&ephemeral=false&namespaceId=public'

Then, went to nacos console, find a service called zipkin-server service, find the cluster configuration, set the health examination mode to TCP, port number of 9411 (zipkin-server port).

Why service registration is successful, the console can't see

This problem appeared in cluster mode, in the use of nacos cluster pattern, ensure that all of the machine time is consistent, can appear otherwise unable to synchronize data.

Nacos principle questions