TiKV node stopped immediately after starting

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

Original topic: tikv 节点启动后直接停了

| username: rw12306

[TiDB Usage Environment] Production Environment / Testing / PoC
[TiDB Version] v5.4.1
[Reproduction Path] What operations were performed when the issue occurred
[Encountered Issue: Issue Phenomenon and Impact]
The TiKV node stops immediately after starting, with the following error message

tikv.rar (1.5 MB)

[Resource Configuration]
[Attachments: Screenshots/Logs/Monitoring]

| username: rw12306 | Original post link

Can someone respond to this error?

| username: xingzhenxiang | Original post link

Check if TiKV has enough disk space and memory. If it doesn’t meet the minimum requirements, it won’t start and will report this issue.

| username: rw12306 | Original post link

The disk and memory are definitely sufficient. Previously, another node reported the same error, and it was resolved after a restart. However, restarting this machine doesn’t work either.
image

| username: rw12306 | Original post link

Take another look for me. Both memory and disk space are sufficient.

| username: Jellybean | Original post link

Judging by the error, it is most likely an environment-related issue. Does the machine deploying TiKV have an SSD?

Alternatively, you can refer to the official documentation for configuration checks:

| username: rw12306 | Original post link

I’ve been using it for a long time. Last time, the ports were restricted and couldn’t access each other. After the ports were opened, it became like this and couldn’t start up.

| username: Jellybean | Original post link

Is this a newly deployed cluster?
Is it a test environment or a production environment?

| username: Hacker007 | Original post link

Try scaling down and then scaling up again.

| username: 魔礼养羊 | Original post link

I suggest you refer to this document, it seems likely that an error in a configuration file is causing the issue.

| username: xingzhenxiang | Original post link

If there are currently 3 TiKV nodes, it is recommended to expand, then shrink, and then expand again to repair the TiKV node. If there are currently more than 3 TiKV nodes, directly shrink and then re-expand the machine.

| username: rw12306 | Original post link

It’s been used in the production environment for a long time.

| username: rw12306 | Original post link

My plan is to do the same, scaling up and down.

| username: 小王同学Plus | Original post link

Hello, is the cluster functioning normally after scaling up or down?