k8s集群中部署nacos集群三节点,当k8s集群的某个node节点宕机后,nacos集群服务可用恢复很慢

bvn4nwqk  于 5个月前  发布在  Nacos
关注(0)|答案(3)|浏览(162)

部署配置

---
apiVersion: v1
kind: Service
metadata:
  name: nacos-headless
  labels:
    app: nacos-headless
spec:
  type: ClusterIP
  clusterIP: None
  ports:
    - port: 8848
      name: server
      targetPort: 8848
    - port: 9848
      name: client-rpc
      targetPort: 9848
    - port: 9849
      name: raft-rpc
      targetPort: 9849
    ## 兼容1.4.x版本的选举端口
    - port: 7848
      name: old-raft-rpc
      targetPort: 7848
  selector:
    app: nacos
---
apiVersion: v1
kind: ConfigMap
metadata:
  name: nacos-cm
data:
  mysql.host: "mysql"
  mysql.db.name: "nacos_devtest"
  mysql.port: "3306"
  mysql.user: "nacos"
  mysql.password: "nacos"
---
apiVersion: apps/v1
kind: StatefulSet
metadata:
  name: nacos
spec:
  serviceName: nacos-headless
  replicas: 3
  template:
    metadata:
      labels:
        app: nacos
      annotations:
        pod.alpha.kubernetes.io/initialized: "true"
    spec:
      affinity:
        podAntiAffinity:
          requiredDuringSchedulingIgnoredDuringExecution:
            - labelSelector:
                matchExpressions:
                  - key: "app"
                    operator: In
                    values:
                      - nacos
              topologyKey: "kubernetes.io/hostname"
      containers:
        - name: nacos
          imagePullPolicy: Always
          image: nacos/nacos-server:latest
          resources:
            requests:
              memory: "2Gi"
              cpu: "500m"
          ports:
            - containerPort: 8848
              name: client
            - containerPort: 9848
              name: client-rpc
            - containerPort: 9849
              name: raft-rpc
            - containerPort: 7848
              name: old-raft-rpc
          env:
            - name: NACOS_REPLICAS
              value: "3"
            - name: MYSQL_SERVICE_HOST
              valueFrom:
                configMapKeyRef:
                  name: nacos-cm
                  key: mysql.host
            - name: MYSQL_SERVICE_DB_NAME
              valueFrom:
                configMapKeyRef:
                  name: nacos-cm
                  key: mysql.db.name
            - name: MYSQL_SERVICE_PORT
              valueFrom:
                configMapKeyRef:
                  name: nacos-cm
                  key: mysql.port
            - name: MYSQL_SERVICE_USER
              valueFrom:
                configMapKeyRef:
                  name: nacos-cm
                  key: mysql.user
            - name: MYSQL_SERVICE_PASSWORD
              valueFrom:
                configMapKeyRef:
                  name: nacos-cm
                  key: mysql.password
            - name: SPRING_DATASOURCE_PLATFORM
              value: "mysql"
            - name: NACOS_SERVER_PORT
              value: "8848"
            - name: NACOS_APPLICATION_PORT
              value: "8848"
            - name: PREFER_HOST_MODE
              value: "hostname"
            - name: NACOS_SERVERS
              value: "nacos-0.nacos-headless.default.svc.cluster.local:8848 nacos-1.nacos-headless.default.svc.cluster.local:8848 nacos-2.nacos-headless.default.svc.cluster.local:8848"
  selector:
    matchLabels:
      app: nacos

nacos客户端版本:1.4.1

jdk:1.8

期望:如果k8s某个node节点宕机,nacos集群可以很快恢复,服务端能快速重连到nacos集群,恢复系统使用

您好,这对k8s某个node节点宕机,nacos集群可以很快恢复,服务端能快速重连到nacos集群,应该怎么进行排查和优化

ql3eal8s

ql3eal8s1#

具体现象是什么? 具体报错是什么?

ltskdhd1

ltskdhd12#

具体现象是什么? 具体报错是什么?

现象:k8s部署nacos集群(三个nacos节点),测试停掉某个node节点,按理解高可用场景nacos集群在较短时间内可以恢复使用,实际访问nacos管理后台查看到配置大概2分钟左右恢复正常
服务重新注册到nacos的过程大概需要8分钟左右

报错信息:目前看nacos leader节点挂掉后,服务重新注册到nacos上时间比较长,目前测试大概
Nacos connection exception, Nacos address: http://nacos-headless:8848/nacos

配置:

集群:

ipakzgxi

ipakzgxi3#

具体现象是什么? 具体报错是什么

目前看当我们宕掉leader节点,在集群中解析 nacos-headless有些问题,请问这个有什么好的处理方式吗

相关问题