Skip to main content
Version: v2.3

Namingserver Registration Center

Namingserver is the native registration center of Seata.

Preparations​

You can choose to run the naming server in the compiler or after packaging it.

Running the naming server in the compiler​

Go to the namingserver directory, set the port number for the naming server in resources/application.yml, and start the naming server.

Running Naming Server​

Download the Seata 2.2.0 binary package from the link and unzip it. Then, enter the seata-namingserver directory.

In the conf/application.yml file, configure the port number for starting the naming server.

For Mac or Linux, run:

bin/seata-namingserver.sh

For Windows, run:

bin/seata-namingserver.bat

Getting Started Quickly​

The process to use the naming server as Seata's registration center is very simple and involves configuring both the client and server sides.

Client-side Configuration for the Registration Center​

Add the corresponding registration center in the application.yml:

seata:
  registry:
    type: seata
  seata:
    server-addr: 127.0.0.1:8081   ## IP + port of the naming server configured in the first step. Use commas to separate multiple naming server nodes.
    namespace: public  ## Namespace
    heartbeat-period: 5000  ## Heartbeat interval

Server-side Configuration for the Registration Center​

Add the following configuration to conf/application.yaml, with the rest of the configuration referring to configuration options:

seata:
  registry:
    type: seata
  seata:
    server-addr: 127.0.0.1:8081   ## IP + port of the naming server configured in the first step. Use commas to separate multiple naming server nodes.
    cluster: default  ## Cluster name
    namespace: public  ## Namespace
    heartbeat-period: 5000  ## Heartbeat interval

Create a Mapping Between the Client's Transaction Group and the Seata Cluster​

Send an HTTP request to one naming server node to create a transaction group-to-cluster mapping (the naming server node will automatically synchronize with other nodes):

http://127.0.0.1:8081/naming/v1/addGroup?clusterName=cluster2&namespace=public&unitName&vGroup=my_test_tx_group

(In this, namespace is the namespace configured on the client side, vGroup is the transaction group configured on the client side, and clusterName is the cluster name on the server side that needs to be mapped.)

Change the Mapping Between the Client's Transaction Group and the Seata Cluster​

Send an HTTP request to one naming server node to change the transaction group-to-cluster mapping (the naming server node will automatically synchronize with other nodes):

http://127.0.0.1:8081/naming/v1/changeGroup?clusterName=cluster2&namespace=public&unitName&vGroup=my_test_tx_group

(In this, namespace is the namespace configured on the client side, vGroup is the transaction group configured on the client side, and clusterName is the cluster name on the server side that needs to be mapped.)

Afterward, once Seata-Server is started and the client configuration is complete, you can begin to experience Seata services.

Tips:

    1. Ensure the client and server registries are in the same namespace, otherwise services won't be found.
    1. Namingserver should only be used on internal networks, never expose it to public networks.
    1. Namingserver is an experimental feature and may change in future versions. Please evaluate and test thoroughly before using in production.
    1. Adding, deleting, or modifying transaction groups must be done through namingserver's open-api. Bypassing this may cause data inconsistency, resulting in service discovery failures or exceptions.