Nacos 3.x 支持PostgreSQL数据库-插件集成-nacos集群

gblfy

1130人浏览 · 2026-01-30 15:53:55

gblfy · 2026-01-30 15:53:55 发布

在这里插入图片描述

文章目录

软件	版本
Nacos版本	3.1.1
操作系统	Centos7
Docker	26.1.4
Docker Compose	v5.0.2
PostgreSQL	PostgreSQL 18.1
Navicat Premium	16.3.3
本地win10运行编译环境	Java 17

一、克隆插件源码

1.1. 本地构建原因

由于该插件是使用Java21编译的，直接运行提示"PostgreSQL插件是用Java 21编译的，但你使用的是Java 17运行时环境",该问题已提交issues，因此需要本地手工编译打包方式获取Java17编译jar。
https://github.com/lilinhai/nacos-datasource-plugin-ext/issues/7
在这里插入图片描述

1.2. 源码克隆

方式1：

git clone https://github.com/lilinhai/nacos-datasource-plugin-ext

方式2：
直接下载
https://github.com/lilinhai/nacos-datasource-plugin-ext/archive/refs/tags/3.1.1.zip

二、本地构建nacos插件

2.1. 设置编译的Java 17

在这里插入图片描述

2.2. 开始构建

mvn clean package -DskipTests -Dgpg.skip=true -Dmaven.javadoc.skip=true

在这里插入图片描述
构建完成后生成nacos-postgresql-datasource-plugin-ext-3.1.1.jar

三、构建镜像准备资料

3.1. application.properties

本地新建nacos3.1.1目录
application.properties

#
# Copyright 1999-2025 Alibaba Group Holding Ltd.
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
#      http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
#

#--------------- Nacos Common Configurations ---------------#

#*************** Nacos port Related Configurations ***************#
### Nacos Server Main port
nacos.server.main.port=${NACOS_APPLICATION_PORT:8848}

#*************** Network Related Configurations ***************#
### If prefer hostname over ip for Nacos server addresses in cluster.conf:
# nacos.inetutils.prefer-hostname-over-ip=false

### Specify local server's IP:
# nacos.inetutils.ip-address=

#*************** Datasource Related Configurations ***************#
### nacos.plugin.datasource.log.enabled=true
spring.sql.init.platform=${SPRING_DATASOURCE_PLATFORM:}
### Count of DB:
# db.num=1

### Connect URL of DB:
db.num=1
db.url.0=jdbc:postgresql://${POSTGRESQL_SERVICE_HOST}:${POSTGRESQL_SERVICE_PORT:5432}/${POSTGRESQL_SERVICE_DB_NAME}?currentSchema=nacos&useUnicode=true&tcpKeepAlive=true&characterEncoding=utf8&serverTimezone=Asia/Shanghai&reWriteBatchedInserts=true&ApplicationName=nacos_java
db.user.0=${POSTGRESQL_SERVICE_USER}
db.password.0=${POSTGRESQL_SERVICE_PASSWORD}
db.pool.config.driverClassName=org.postgresql.Driver

db.pool.config.connectionTimeout=${DB_POOL_CONNECTION_TIMEOUT:30000}
db.pool.config.validationTimeout=10000
db.pool.config.maximumPoolSize=20
db.pool.config.minimumIdle=2

#*************** Metrics Related Configurations ***************#
### Metrics for prometheus
management.endpoints.web.exposure.include=prometheus

### Metrics for elastic search
management.metrics.export.elastic.enabled=false
#management.metrics.export.elastic.host=http://localhost:9200

### Metrics for influx
management.metrics.export.influx.enabled=false
#management.metrics.export.influx.db=springboot
#management.metrics.export.influx.uri=http://localhost:8086
#management.metrics.export.influx.auto-create-db=true
#management.metrics.export.influx.consistency=one
#management.metrics.export.influx.compressed=true

#*************** Core Related Configurations ***************#

### set the WorkerID manually
# nacos.core.snowflake.worker-id=

### Member-MetaData
# nacos.core.member.meta.site=
# nacos.core.member.meta.adweight=
# nacos.core.member.meta.weight=

### MemberLookup
### Addressing pattern category, If set, the priority is highest
# nacos.core.member.lookup.type=[file,address-server]

## Set the cluster list with a configuration file or command-line argument
# nacos.member.list=192.168.16.101:8847?raft_port=8807,192.168.16.101?raft_port=8808,192.168.16.101:8849?raft_port=8809

## for AddressServerMemberLookup
# Maximum number of retries to query the address server upon initialization
# nacos.core.address-server.retry=5
## Server domain name address of [address-server] mode
# address.server.domain=jmenv.tbsite.net
## Server port of [address-server] mode
# address.server.port=8080
## Request address of [address-server] mode
# address.server.url=/nacos/serverlist

# 解决jmenv.tbsite.net连接问题
nacos.core.member.lookup.type=file
nacos.member.list=${NACOS_SERVERS:}

#*************** JRaft Related Configurations ***************#

### Sets the Raft cluster election timeout, default value is 5 second
# nacos.core.protocol.raft.data.election_timeout_ms=5000
### Sets the amount of time the Raft snapshot will execute periodically, default is 30 minute
# nacos.core.protocol.raft.data.snapshot_interval_secs=30
### raft internal worker threads
# nacos.core.protocol.raft.data.core_thread_num=8
### Number of threads required for raft business request processing
# nacos.core.protocol.raft.data.cli_service_thread_num=4
### raft linear read strategy. Safe linear reads are used by default, that is, the Leader tenure is confirmed by heartbeat
# nacos.core.protocol.raft.data.read_index_type=ReadOnlySafe
### rpc request timeout, default 5 seconds
# nacos.core.protocol.raft.data.rpc_request_timeout_ms=5000
### enable to support prometheus service discovery
#nacos.prometheus.metrics.enabled=true

#*************** Distro Related Configurations ***************#

### Distro data sync delay time, when sync task delayed, task will be merged for same data key. Default 1 second.
# nacos.core.protocol.distro.data.sync.delayMs=1000
### Distro data sync timeout for one sync data, default 3 seconds.
# nacos.core.protocol.distro.data.sync.timeoutMs=3000
### Distro data sync retry delay time when sync data failed or timeout, same behavior with delayMs, default 3 seconds.
# nacos.core.protocol.distro.data.sync.retryDelayMs=3000
### Distro data verify interval time, verify synced data whether expired for a interval. Default 5 seconds.
# nacos.core.protocol.distro.data.verify.intervalMs=5000
### Distro data verify timeout for one verify, default 3 seconds.
# nacos.core.protocol.distro.data.verify.timeoutMs=3000
### Distro data load retry delay when load snapshot data failed, default 30 seconds.
# nacos.core.protocol.distro.data.load.retryDelayMs=30000
### enable to support prometheus service discovery
#nacos.prometheus.metrics.enabled=true

#*************** Grpc Configurations ***************#

### Sets the maximum message size allowed to be received on the server.
#nacos.remote.server.grpc.sdk.max-inbound-message-size=10485760
### Sets the time(milliseconds) without read activity before sending a keepalive ping. The typical default is two hours.
#nacos.remote.server.grpc.sdk.keep-alive-time=7200000
### Sets a time(milliseconds) waiting for read activity after sending a keepalive ping. Defaults to 20 seconds.
#nacos.remote.server.grpc.sdk.keep-alive-timeout=20000
### Sets a time(milliseconds) that specify the most aggressive keep-alive time clients are permitted to configure. The typical default is 5 minutes
#nacos.remote.server.grpc.sdk.permit-keep-alive-time=300000
### cluster grpc(inside the nacos server) configuration
#nacos.remote.server.grpc.cluster.max-inbound-message-size=10485760
### Sets the time(milliseconds) without read activity before sending a keepalive ping. The typical default is two hours.
#nacos.remote.server.grpc.cluster.keep-alive-time=7200000
### Sets a time(milliseconds) waiting for read activity after sending a keepalive ping. Defaults to 20 seconds.
#nacos.remote.server.grpc.cluster.keep-alive-timeout=20000
### Sets a time(milliseconds) that specify the most aggressive keep-alive time clients are permitted to configure. The typical default is 5 minutes
#nacos.remote.server.grpc.cluster.permit-keep-alive-time=300000

#*************** Config Module Related Configurations ***************#

### the maximum retry times for push
nacos.config.push.maxRetryTime=50

#*************** Naming Module Related Configurations ***************#
### Data dispatch task execution period in milliseconds:

### If enable data warmup. If set to false, the server would accept request without local data preparation:
nacos.naming.data.warmup=true

### If enable the instance auto expiration, kind like of health check of instance:
# nacos.naming.expireInstance=true

nacos.naming.empty-service.auto-clean=true
nacos.naming.empty-service.clean.initial-delay-ms=50000
nacos.naming.empty-service.clean.period-time-ms=30000

#--------------- Nacos Web Server Configurations ---------------#

#*************** Nacos Web Server Related Configurations ***************#
### Nacos Server Web context path:
nacos.server.contextPath=${SERVER_SERVLET_CONTEXTPATH:/nacos}

#*************** Access Log Related Configurations ***************#
### If turn on the access log:
server.tomcat.accesslog.enabled=true

### accesslog automatic cleaning time
server.tomcat.accesslog.max-days=30

### The access log pattern:
server.tomcat.accesslog.pattern=%h %l %u %t "%r" %s %b %D %{User-Agent}i %{Request-Source}i

### The directory of access log:
server.tomcat.basedir=file:.

#*************** API Related Configurations ***************#
### Include message field
server.error.include-message=ALWAYS

### Enabled for open API compatibility
# nacos.core.api.compatibility.client.enabled=true
### Enabled for admin API compatibility
# nacos.core.api.compatibility.admin.enabled=false
### Enabled for console API compatibility
# nacos.core.api.compatibility.console.enabled=false

#--------------- Nacos Console Configurations ---------------#

#*************** Nacos Console Related Configurations ***************#
### Nacos Console Main port
nacos.console.port=${NACOS_CONSOLE_PORT:8080}
### Nacos Server Web context path:
nacos.console.contextPath=${NACOS_CONSOLE_CONTEXTPATH:}

### Nacos Server context path, which link to nacos server `nacos.server.contextPath`, works when deployment type is `console`
nacos.console.remote.server.context-path=${SERVER_SERVLET_CONTEXTPATH:/nacos}

#************** Console UI Configuration ***************#

### Turn on/off the nacos console ui.
nacos.console.ui.enabled=true

#--------------- Nacos Plugin Configurations ---------------#

#*************** CMDB Plugin Related Configurations ***************#
### The interval to dump external CMDB in seconds:
# nacos.cmdb.dumpTaskInterval=3600

### The interval of polling data change event in seconds:
# nacos.cmdb.eventTaskInterval=10

### The interval of loading labels in seconds:
# nacos.cmdb.labelTaskInterval=300

### If turn on data loading task:
# nacos.cmdb.loadDataAtStart=false

#*************** Auth Plugin Related Configurations ***************#
### The ignore urls of auth, will be deprecated in the future:
nacos.security.ignore.urls=${NACOS_SECURITY_IGNORE_URLS:/,/error,/**/*.css,/**/*.js,/**/*.html,/**/*.map,/**/*.svg,/**/*.png,/**/*.ico,/console-fe/public/**,/v1/auth/**,/v1/console/health/**,/actuator/**,/v1/console/server/**}

### The auth system to use, default 'nacos' and 'ldap' is supported, other type should be implemented by yourself:
nacos.core.auth.system.type=${NACOS_AUTH_SYSTEM_TYPE:nacos}

### If turn on auth system:
# Whether open nacos server API auth system
nacos.core.auth.enabled=false
# Whether open nacos admin API auth system
nacos.core.auth.admin.enabled=true
# Whether open nacos console API auth system
nacos.core.auth.console.enabled=true

### Turn on/off caching of auth information. By turning on this switch, the update of auth information would have a 15 seconds delay.
nacos.core.auth.caching.enabled=${NACOS_AUTH_CACHE_ENABLE:false}

### worked when nacos.core.auth.enabled=true
### The two properties is the white list for auth and used by identity the request from other server.
nacos.core.auth.server.identity.key=${NACOS_AUTH_IDENTITY_KEY:}
nacos.core.auth.server.identity.value=${NACOS_AUTH_IDENTITY_VALUE:}

### worked when nacos.core.auth.system.type=nacos or nacos.core.auth.console.enabled=true
### The token expiration in seconds:
nacos.core.auth.plugin.nacos.token.cache.enable=false
nacos.core.auth.plugin.nacos.token.expire.seconds=${NACOS_AUTH_TOKEN_EXPIRE_SECONDS:18000}
### The default token (Base64 string):
#nacos.core.auth.plugin.nacos.token.secret.key=VGhpc0lzTXlDdXN0b21TZWNyZXRLZXkwMTIzNDU2Nzg=
nacos.core.auth.plugin.nacos.token.secret.key=${NACOS_AUTH_TOKEN:}

### worked when nacos.core.auth.system.type=ldap?{0} is Placeholder,replace login username
#nacos.core.auth.ldap.url=ldap://localhost:389
#nacos.core.auth.ldap.basedc=dc=example,dc=org
#nacos.core.auth.ldap.userDn=cn=admin,${nacos.core.auth.ldap.basedc}
#nacos.core.auth.ldap.password=admin
#nacos.core.auth.ldap.userdn=cn={0},dc=example,dc=org
#nacos.core.auth.ldap.filter.prefix=uid
#nacos.core.auth.ldap.case.sensitive=true
#nacos.core.auth.ldap.ignore.partial.result.exception=false

#*************** Control Plugin Related Configurations ***************#
# plugin type
#nacos.plugin.control.manager.type=nacos

# local control rule storage dir, default ${nacos.home}/data/connection and ${nacos.home}/data/tps
#nacos.plugin.control.rule.local.basedir=${nacos.home}

# external control rule storage type, if exist
#nacos.plugin.control.rule.external.storage=

#*************** Config Change Plugin Related Configurations ***************#
# webhook
#nacos.core.config.plugin.webhook.enabled=false
# It is recommended to use EB https://help.aliyun.com/document_detail/413974.html
#nacos.core.config.plugin.webhook.url=http://localhost:8080/webhook/send?token=***
# The content push max capacity ,byte
#nacos.core.config.plugin.webhook.contentMaxCapacity=102400

# whitelist
#nacos.core.config.plugin.whitelist.enabled=false
# The import file suffixs
#nacos.core.config.plugin.whitelist.suffixs=xml,text,properties,yaml,html
# fileformatcheck,which validate the import file of type and content
#nacos.core.config.plugin.fileformatcheck.enabled=false

#*************** Istio Plugin Related Configurations ***************#
### If turn on the MCP server:
nacos.istio.mcp.server.enabled=false

#--------------- Nacos Experimental Features Configurations ---------------#

#*************** K8s Related Configurations ***************#
### If turn on the K8s sync:
nacos.k8s.sync.enabled=false

### If use the Java API from an application outside a kubernetes cluster
#nacos.k8s.sync.outsideCluster=false
#nacos.k8s.sync.kubeConfig=/.kube/config

#*************** Deployment Type Configuration ***************#

### Sets the deployment type: 'merged' for joint deployment, 'server' for separate deployment server only, 'console' for separate deployment console only.
nacos.deployment.type=merged

3.2. Dockerfile

FROM nacos/nacos-server:v3.1.1 

COPY application.properties /home/nacos/conf/
COPY nacos-postgresql-datasource-plugin-ext-3.1.1.jar   /home/nacos/plugins/
CMD ["sh", "-c", "bin/docker-startup.sh"]

如果是公司的话，这一行FROM nacos/nacos-server:v3.1.1 换成公司私库
nacos-postgresql-datasource-plugin-ext-3.1.1.jar

3.3. nacos-postgresql-datasource-plugin-ext

构建完成后生成nacos-postgresql-datasource-plugin-ext-3.1.1.jar(上面已生成)，登录Centos7，新建/app目录

mkdir /app

将上面3个资料上传Centos7的/app目录

四、集群部署

4.1. 构建nacos镜像

# 构建镜像
docker build -t nacos-postgresql:3.1.1 .

# 验证构建成功
docker images | grep nacos-postgresql

4.2. 创建部署目录

# 创建集群目录结构
mkdir -p /app/nacos-cluster
cd /app/nacos-cluster
mkdir -p logs/{node1,node2,node3} data/{node1,node2,node3}

4.3. 下载配置docker-compose

# 下载最新稳定版 Docker Compose
sudo curl -L "https://github.com/docker/compose/releases/latest/download/docker-compose-$(uname -s)-$(uname -m)" -o /usr/local/bin/docker-compose

chmod +x /usr/local/bin/docker-compose
ln -s /usr/local/bin/docker-compose /usr/bin/docker-compose
docker-compose --version

4.4. 新建docker-compose.yml（单节点）

新建单节点的目的是，先测试单节点没问题，有问题提前调整，避免出现简单的问题，增加额外耗时。

cat > docker-compose.yml << 'EOF'
version: '3.8'
services:
  nacos-node1:
    image: nacos-postgresql:3.1.1
    container_name: nacos-node1
    hostname: nacos-node1
    restart: unless-stopped
    ports:
      - "8848:8848"
      - "8080:8080"
      - "9848:9848"
    environment:
      - MODE=standalone
      - NACOS_APPLICATION_PORT=8848
      - PREFER_HOST_MODE=hostname
      - SPRING_DATASOURCE_PLATFORM=postgresql
      - POSTGRESQL_SERVICE_HOST=host.docker.internal
      - POSTGRESQL_SERVICE_PORT=5432
      - POSTGRESQL_SERVICE_DB_NAME=mydatabase
      - POSTGRESQL_SERVICE_USER=myuser
      - POSTGRESQL_SERVICE_PASSWORD=mysecretpassword
      - NACOS_AUTH_ENABLE=false
      - NACOS_AUTH_TOKEN=VGhpc0lzTXlDdXN0b21TZWNyZXRLZXkwMTIzNDU2Nzg=
      - NACOS_AUTH_IDENTITY_KEY=serverIdentity
      - NACOS_AUTH_IDENTITY_VALUE=security
      - JVM_XMS=512m
      - JVM_XMX=512m
      - JVM_XMN=256m
    extra_hosts:
      - "host.docker.internal:host-gateway"
    volumes:
      - ./logs/node1:/home/nacos/logs
      - ./data/node1:/home/nacos/data
    networks:
      - nacos-net

networks:
  nacos-net:
    driver: bridge
    ipam:
      config:
        - subnet: 172.30.0.0/16
EOF

4.5. 新建docker-compose.yml（集群节点）

cat > docker-compose.yml << 'EOF'
version: '3.8'
services:
  nacos-node1:
    image: nacos-postgresql:3.1.1
    container_name: nacos-node1
    hostname: nacos-node1
    restart: unless-stopped
    ports:
      - "8848:8848"
      - "8080:8080"
      - "9848:9848"
    environment:
      - MODE=cluster
      - NACOS_APPLICATION_PORT=8848
      - PREFER_HOST_MODE=hostname
      - SPRING_DATASOURCE_PLATFORM=postgresql
      - POSTGRESQL_SERVICE_HOST=host.docker.internal
      - POSTGRESQL_SERVICE_PORT=5432
      - POSTGRESQL_SERVICE_DB_NAME=mydatabase
      - POSTGRESQL_SERVICE_USER=myuser
      - POSTGRESQL_SERVICE_PASSWORD=mysecretpassword
      - NACOS_SERVERS=nacos-node1:8848,nacos-node2:8848,nacos-node3:8848
      - NACOS_AUTH_ENABLE=false
      - NACOS_AUTH_TOKEN=VGhpc0lzTXlDdXN0b21TZWNyZXRLZXkwMTIzNDU2Nzg=
      - NACOS_AUTH_IDENTITY_KEY=serverIdentity
      - NACOS_AUTH_IDENTITY_VALUE=security
      - JVM_XMS=512m
      - JVM_XMX=512m
      - JVM_XMN=256m
    extra_hosts:
      - "host.docker.internal:host-gateway"
    volumes:
      - ./logs/node1:/home/nacos/logs
      - ./data/node1:/home/nacos/data
    networks:
      - nacos-net

  nacos-node2:
    image: nacos-postgresql:3.1.1
    container_name: nacos-node2
    hostname: nacos-node2
    restart: unless-stopped
    ports:
      - "8849:8848"
      - "8081:8080"
      - "9849:9848"
    environment:
      - MODE=cluster
      - NACOS_APPLICATION_PORT=8848
      - PREFER_HOST_MODE=hostname
      - SPRING_DATASOURCE_PLATFORM=postgresql
      - POSTGRESQL_SERVICE_HOST=host.docker.internal
      - POSTGRESQL_SERVICE_PORT=5432
      - POSTGRESQL_SERVICE_DB_NAME=mydatabase
      - POSTGRESQL_SERVICE_USER=myuser
      - POSTGRESQL_SERVICE_PASSWORD=mysecretpassword
      - NACOS_SERVERS=nacos-node1:8848,nacos-node2:8848,nacos-node3:8848
      - NACOS_AUTH_ENABLE=false
      - NACOS_AUTH_TOKEN=VGhpc0lzTXlDdXN0b21TZWNyZXRLZXkwMTIzNDU2Nzg=
      - NACOS_AUTH_IDENTITY_KEY=serverIdentity
      - NACOS_AUTH_IDENTITY_VALUE=security
      - JVM_XMS=512m
      - JVM_XMX=512m
      - JVM_XMN=256m
    extra_hosts:
      - "host.docker.internal:host-gateway"
    volumes:
      - ./logs/node2:/home/nacos/logs
      - ./data/node2:/home/nacos/data
    depends_on:
      - nacos-node1
    networks:
      - nacos-net

  nacos-node3:
    image: nacos-postgresql:3.1.1
    container_name: nacos-node3
    hostname: nacos-node3
    restart: unless-stopped
    ports:
      - "8850:8848"
      - "8082:8080"
      - "9850:9848"
    environment:
      - MODE=cluster
      - NACOS_APPLICATION_PORT=8848
      - PREFER_HOST_MODE=hostname
      - SPRING_DATASOURCE_PLATFORM=postgresql
      - POSTGRESQL_SERVICE_HOST=host.docker.internal
      - POSTGRESQL_SERVICE_PORT=5432
      - POSTGRESQL_SERVICE_DB_NAME=mydatabase
      - POSTGRESQL_SERVICE_USER=myuser
      - POSTGRESQL_SERVICE_PASSWORD=mysecretpassword
      - NACOS_SERVERS=nacos-node1:8848,nacos-node2:8848,nacos-node3:8848
      - NACOS_AUTH_ENABLE=false
      - NACOS_AUTH_TOKEN=VGhpc0lzTXlDdXN0b21TZWNyZXRLZXkwMTIzNDU2Nzg=
      - NACOS_AUTH_IDENTITY_KEY=serverIdentity
      - NACOS_AUTH_IDENTITY_VALUE=security
      - JVM_XMS=512m
      - JVM_XMX=512m
      - JVM_XMN=256m
    extra_hosts:
      - "host.docker.internal:host-gateway"
    volumes:
      - ./logs/node3:/home/nacos/logs
      - ./data/node3:/home/nacos/data
    depends_on:
      - nacos-node2
    networks:
      - nacos-net

networks:
  nacos-net:
    driver: bridge
    ipam:
      config:
        - subnet: 172.30.0.0/16
EOF

五、pg数据库新建和初始化

5.1. 新建pg数据库

docker run -d \
  --name postgres \
  -e POSTGRES_PASSWORD=mysecretpassword \
  -e POSTGRES_USER=myuser \
  -e POSTGRES_DB=mydatabase \
  -e PGDATA=/var/lib/postgresql/data/pgdata \
  -p 5432:5432 \
  -v ~/docker/postgres/data:/var/lib/postgresql/data \
  --restart unless-stopped \
  postgres:latest

5.2. 新建nacos schema

方式1（宿主机）：

# 1. 创建nacos schema并设置权限
docker run --rm --add-host=host.docker.internal:host-gateway -e PGPASSWORD=mysecretpassword postgres:latest \
psql -h host.docker.internal -U myuser -d mydatabase -c "
CREATE SCHEMA IF NOT EXISTS nacos;
GRANT ALL ON SCHEMA nacos TO myuser;
GRANT ALL PRIVILEGES ON ALL TABLES IN SCHEMA nacos TO myuser;
GRANT ALL PRIVILEGES ON ALL SEQUENCES IN SCHEMA nacos TO myuser;
ALTER USER myuser SET search_path TO nacos,public;
"

方式2（Navicat）：

CREATE SCHEMA IF NOT EXISTS nacos;
GRANT ALL ON SCHEMA nacos TO myuser;
GRANT ALL PRIVILEGES ON ALL TABLES IN SCHEMA nacos TO myuser;
GRANT ALL PRIVILEGES ON ALL SEQUENCES IN SCHEMA nacos TO myuser;
ALTER USER myuser SET search_path TO nacos,public;

5.3. 初始化表结构

nacos-pg-v3.1.1.sql，在nacos的schema下面执行才可以(很重要)，因为在application.properties中已经指定了db.url.0=jdbc:postgresql://${POSTGRESQL_SERVICE_HOST}:${POSTGRESQL_SERVICE_PORT:5432}/${POSTGRESQL_SERVICE_DB_NAME}?currentSchema=nacos&useUnicode=true&tcpKeepAlive=true&characterEncoding=utf8&serverTimezone=Asia/Shanghai&reWriteBatchedInserts=true&ApplicationName=nacos_java
在这里插入图片描述

六、集群操作

单节点
和集群命令一样的
集群节点

6.1. 启动所有节点

docker-compose up -d

6.2. 查看启动状态

docker-compose ps

6.3. 查看启动日志

docker-compose logs -f

停止服务命令

docker-compose down

七、测试验证

### 访问控制台
- Node1: http://your-server-ip:8848/nacos
- Node2: http://your-server-ip:8849/nacos
- Node3: http://your-server-ip:8850/nacos

登录信息: nacos/nacos

7.1. 集群节点验证

在这里插入图片描述

7.2. 集群状态

在这里插入图片描述

八、防火墙配置

8.1. 开放必要端口

sudo firewall-cmd --permanent --add-port=8848/tcp
sudo firewall-cmd --permanent --add-port=8849/tcp
sudo firewall-cmd --permanent --add-port=8850/tcp
sudo firewall-cmd --permanent --add-port=9848/tcp
sudo firewall-cmd --permanent --add-port=9849/tcp
sudo firewall-cmd --permanent --add-port=9850/tcp

8.2. 重载防火墙

sudo firewall-cmd --reload

九、常用管理命令

# 查看所有容器状态
docker-compose ps

# 重启整个集群
docker-compose restart

# 重启单个节点
docker-compose restart nacos-node1

# 查看实时日志
docker-compose logs -f nacos-node1

# 停止集群
docker-compose down

# 强制重建容器
docker-compose up -d --force-recreate

腾讯云开发者社区

腾讯云面向开发者汇聚海量精品云计算使用和开发经验，营造开放的云计算技术生态圈。

更多推荐

终极指南：Flink SQL连接器版本管理从混乱到有序的升级之路

Apache Flink作为流处理领域的佼佼者，其SQL连接器的版本管理一直是开发者面临的核心挑战。本文将系统讲解Flink SQL连接器版本管理的最佳实践，帮助你轻松应对版本兼容性问题，实现从混乱到有序的升级之旅。## 连接器版本管理的常见痛点 😫在Flink应用开发中，连接器版本管理常常让开发者头疼不已。不同版本的连接器可能导致各种兼容性问题，例如API变更、功能差异甚至运行时错误。

腾讯云开发者社区

Elasticsearch复杂数据类型终极指南：从入门到精通

Elasticsearch作为功能强大的搜索引擎，支持多种复杂数据类型，让开发者能够灵活处理各种结构化和非结构化数据。本文将带你全面了解Elasticsearch中的复杂数据类型，从基础概念到实际应用，助你轻松掌握数据建模的核心技巧。## 内部对象：构建层级化数据结构在Elasticsearch中，对象类型（Object）是最基础的复杂数据类型之一，用于表示具有嵌套关系的数据。例如，我们可

腾讯云开发者社区

如何快速搭建Neon无服务器PostgreSQL：面向初学者的完整指南

Neon是一款革命性的无服务器PostgreSQL解决方案，它通过分离存储和计算层，实现了自动扩缩容、类代码式数据库分支以及零级扩展能力。本指南将帮助你从零开始搭建Neon开发环境，体验这款创新数据库的强大功能。## 准备工作：环境要求与依赖项在开始搭建Neon环境前，请确保你的系统满足以下要求：- Linux操作系统（推荐Ubuntu 20.04+或Debian 11+）- Git