1 startup parameters
1.1 Source code
@Parameter(names = "--help", help = true)
private boolean help;
@Parameter(names = {
"--host", "-h"}, description = "The ip to register to registry center.", order = 1)
private String host;
@Parameter(names = {
"--port", "-p"}, description = "The port to listen.", order = 2)
private int port = SERVER_DEFAULT_PORT;
@Parameter(names = {
"--storeMode", "-m"}, description = "log store mode : file, db", order = 3)
private String storeMode;
@Parameter(names = {
"--serverNode", "-n"}, description = "server node id, such as 1, 2, 3.it will be generated according to the snowflake by default", order = 4)
private Long serverNode;
@Parameter(names = {
"--seataEnv", "-e"}, description = "The name used for multi-configuration isolation.",
order = 5)
private String seataEnv;
1.2 Description
| parameter | illustrate |
|---|---|
| –help | View help |
| –host, -h | Server-side IP, if the input is -h 192.168.8.8, the registered address in nacos is the current address, which can be used in a multi-network card environment. |
| –port, -p | Server side startup and listening port |
| –storeMode, -m | Log storage method, supports file, db |
| –serverNode, -n | serverNode is the serial number used to distinguish nodes in the TC cluster. The branch transaction ID and various IDs generated by each node are generated based on this node. The interval is 2 billion. For example, -n 1 node will probably generate IDs starting with 2, -n 2 The generated ID starts with 4, in order to avoid duplication of xid |
| –seataEnv, -e | Multi-environment configuration of the registry.conf file, for example, modify the configuration file to registry-dev.conf and add -e dev to start, the configuration of the dev environment will be read |
2 Configuration parameters
2.1 Communication part
2.2 Server
2.3 Client
2.4 Storage
2.5 Monitoring
