Deploying TiDB v5.4.1 on k8s, TiKV remains in CrashLoopBackOff state indicating connection issues, problem persists despite modifications

Translated
1

Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: k8s 部署 tidbv5.4.1，tikv 一直处于 CrashLoopBackOff 状态 提示连接数问题，已修改问题没解决

| username: TiDBer_IRSbNCAt
  • tidb: v5.4.1
  • tidb-operator: v1.3.7
  • k8s: v1.18.6
  • os: centos7.6
  • 3.10.0-957.el7.x86_64

In this environment, deploying results in TiKV being stuck in CrashLoopBackOff.
image
Checking the logs reveals that the issue is related to the maximum number of open file descriptors being too small.

image
image1208×658 30.9 KB

Afterwards, I modified the system’s ulimit.
image
I also modified Docker’s LimitNOFILE settings.
image
image713×505 13.9 KB

The problem persists.
Docker’s configuration is as follows:
image
Can any expert help take a look?

2
| username: TiDBer_jYQINSnf | Original post link

Modify the ulimit of a k8s node

3
| username: wuxiangdong | Original post link

ps -ef | grep k8s
cat /proc/process_id/limits to see how much is inside the process

4
| username: TiDBer_IRSbNCAt | Original post link

Thank you, I found the answer to the problem. Initially, I only checked the limits of Docker and didn’t check the container itself. Now it’s resolved, thank you very much.

5
| username: system | Original post link

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.