Unable to establish connection when select and insert（in k8s environment）

[susumumuqiqi]

您好，我目前在k8s上部署了一个单节点tdengine，版本是：2.4.0.26，6030-6042 端口的 TCP/UDP 也全都开了，服务能正常启动，客户端也能连上，但在执行 select 时，��报"Unable to establish connection"异常，我根据这个错误在贵平台错误处理进行了排查，还是没法解决，不知有没有其它的一些建议可以提供

[susumumuqiqi]

以下是我在k8s上部署tdengine的yaml文件：

---

apiVersion: apps/v1
kind: StatefulSet
metadata:
labels:
app: tde
k8s.kuboard.cn/layer: cloud
k8s.kuboard.cn/name: tde
name: tde
namespace: canos
spec:
podManagementPolicy: OrderedReady
replicas: 1
revisionHistoryLimit: 10
selector:
matchLabels:
app: tde
k8s.kuboard.cn/layer: cloud
k8s.kuboard.cn/name: tde
serviceName: tde
template:
metadata:
annotations:
kubectl.kubernetes.io/restartedAt: '2023-05-17T09:29:48+08:00'
creationTimestamp: null
labels:
app: tde
k8s.kuboard.cn/layer: cloud
k8s.kuboard.cn/name: tde
spec:
containers:
- env:
- name: TAOS_FQDN
value: tde-0.tde.canos.svc.cluster.local
- name: TZ
value: Asia/Shanghai
image: 'tdengine/tdengine:2.4.0.26'
imagePullPolicy: Always
name: tde
ports:
- containerPort: 6030
protocol: TCP
- containerPort: 6030
protocol: UDP
- containerPort: 6031
protocol: TCP
- containerPort: 6031
protocol: UDP
- containerPort: 6032
protocol: TCP
- containerPort: 6032
protocol: UDP
- containerPort: 6033
protocol: TCP
- containerPort: 6033
protocol: UDP
- containerPort: 6034
protocol: TCP
- containerPort: 6034
protocol: UDP
- containerPort: 6035
protocol: TCP
- containerPort: 6035
protocol: UDP
- containerPort: 6036
protocol: TCP
- containerPort: 6036
protocol: UDP
- containerPort: 6037
protocol: TCP
- containerPort: 6037
protocol: UDP
- containerPort: 6038
protocol: TCP
- containerPort: 6038
protocol: UDP
- containerPort: 6039
protocol: TCP
- containerPort: 6039
protocol: UDP
- containerPort: 6040
protocol: TCP
- containerPort: 6040
protocol: UDP
- containerPort: 6041
protocol: TCP
- containerPort: 6041
protocol: UDP
- containerPort: 6042
protocol: TCP
- containerPort: 6042
protocol: UDP
resources: {}
terminationMessagePath: /dev/termination-log
terminationMessagePolicy: File
volumeMounts:
- mountPath: /var/lib/taos
name: tde-pvc
dnsPolicy: ClusterFirst
restartPolicy: Always
schedulerName: default-scheduler
securityContext: {}
terminationGracePeriodSeconds: 30
updateStrategy:
rollingUpdate:
partition: 0
type: RollingUpdate
volumeClaimTemplates:
- apiVersion: v1
kind: PersistentVolumeClaim
metadata:
annotations:
k8s.kuboard.cn/pvcType: Dynamic
creationTimestamp: null
name: tde-pvc
spec:
accessModes:
- ReadWriteMany
resources:
requests:
storage: 1Gi
storageClassName: c1-storage-1
volumeMode: Filesystem
status:
phase: Pending

---

apiVersion: v1
kind: Service
metadata:
labels:
app: tde
k8s.kuboard.cn/layer: cloud
k8s.kuboard.cn/name: tde
name: tde
namespace: canos
spec:
externalTrafficPolicy: Cluster
ports:
- name: ir7jhq
nodePort: 30730
port: 6030
protocol: TCP
targetPort: 6030
- name: yk7xaa
nodePort: 30730
port: 6030
protocol: UDP
targetPort: 6030
- name: p4qkpp
nodePort: 30731
port: 6031
protocol: TCP
targetPort: 6031
- name: ys27wz
nodePort: 30731
port: 6031
protocol: UDP
targetPort: 6031
- name: h546zp
nodePort: 30732
port: 6032
protocol: TCP
targetPort: 6032
- name: 6r432e
nodePort: 30732
port: 6032
protocol: UDP
targetPort: 6032
- name: kxpf4r
nodePort: 30733
port: 6033
protocol: TCP
targetPort: 6033
- name: 2h7f2k
nodePort: 30733
port: 6033
protocol: UDP
targetPort: 6033
- name: 3zfmdw
nodePort: 30734
port: 6034
protocol: TCP
targetPort: 6034
- name: efdax7
nodePort: 30734
port: 6034
protocol: UDP
targetPort: 6034
- name: htwixj
nodePort: 30735
port: 6035
protocol: TCP
targetPort: 6035
- name: mzdhai
nodePort: 30735
port: 6035
protocol: UDP
targetPort: 6035
- name: bkbnbr
nodePort: 30736
port: 6036
protocol: TCP
targetPort: 6036
- name: scbcss
nodePort: 30736
port: 6036
protocol: UDP
targetPort: 6036
- name: mejtry
nodePort: 30737
port: 6037
protocol: TCP
targetPort: 6037
- name: ayzzz6
nodePort: 30737
port: 6037
protocol: UDP
targetPort: 6037
- name: 7gath4
nodePort: 30738
port: 6038
protocol: TCP
targetPort: 6038
- name: bqgakt
nodePort: 30738
port: 6038
protocol: UDP
targetPort: 6038
- name: jsf4ee
nodePort: 30739
port: 6039
protocol: TCP
targetPort: 6039
- name: c2axjy
nodePort: 30739
port: 6039
protocol: UDP
targetPort: 6039
- name: t3txkn
nodePort: 30740
port: 6040
protocol: TCP
targetPort: 6040
- name: pphstr
nodePort: 30740
port: 6040
protocol: UDP
targetPort: 6040
- name: zxmmqm
nodePort: 30741
port: 6041
protocol: TCP
targetPort: 6041
- name: dk2hmi
nodePort: 30741
port: 6041
protocol: UDP
targetPort: 6041
- name: jqehem
nodePort: 30742
port: 6042
protocol: TCP
targetPort: 6042
- name: mzaebd
nodePort: 30742
port: 6042
protocol: UDP
targetPort: 6042
selector:
app: tde
k8s.kuboard.cn/layer: cloud
k8s.kuboard.cn/name: tde
sessionAffinity: None
type: NodePort

[sangshuduo]

具体什么 SQL？单机部署的时候有问题吗？大概率是碰到老版本的 bug 了，建议尽快升级到最新版本

[susumumuqiqi]

taos> use log; (正常执行)
taos> select * from dn1; (报 Unable to establish connection 异常)
单机部署的时候没问题，服务可正常启动，在服务端也能正常执行以上语句，但是通过客户端连上后执行 select 会有异常

[susumumuqiqi]

另外，您说的老版本bug，指的是在k8s环境下的bug吗？因为我们在docker环境下也部了一个相同版本的tdengine，是正常的。

[sangshuduo]

taos> use log; (正常执行) taos> select * from dn1; (报 Unable to establish connection 异常) 单机部署的时候没问题，服务可正常启动，在服务端也能正常执行以上语句，但是通过客户端连上后执行 select 会有异常

看起来像网络问题，可以根据官网 FAQ 章节排查

[luojiyin1987]

建议提供网络捉包数据