Restarting TiKV After a Crash

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

Original topic: tikv宕机后重启

| username: tidb狂热爱好者

[TiDB Usage Environment] Production Environment / Testing / Poc
[TiDB Version] 6.3
[Reproduction Path] What operations were performed when the issue occurred
[Encountered Issue: Issue Phenomenon and Impact]
service tikv-20160 start
Error reported
failed to create engine log dir file exists (os error 17)
[Resource Configuration]
[Attachments: Screenshots / Logs / Monitoring]

| username: Jiawei | Original post link

Normally, there should be an automatic restart. Check if the process exists. If it doesn’t, look at the corresponding directory or the TiKV error log information. The information provided is too limited, so this is as much as I can analyze.

| username: xfworld | Original post link

When describing the problem, please follow:
【TiDB Usage Environment】Production Environment / Testing / PoC
【TiDB Version】
【Problem Phenomenon and Impact】
【Reproduction Path】What operations were performed that led to the problem
【Resource Configuration】

Describe as much effective background information as possible. Many issues may have different suggestions under different scenarios and business contexts. Not explaining clearly will only make it difficult for everyone to help~

| username: h5n1 | Original post link

Let’s talk about how the previous issues were handled.

| username: 我是咖啡哥 | Original post link

What caused the crash? Where are the complete logs?

| username: tidb狂热爱好者 | Original post link

The disk is broken.

| username: tidb菜鸟一只 | Original post link

Is the error that the disk file cannot be found? Is the disk damaged?

| username: 会飞的土拨鼠 | Original post link

The information provided is too little. Based on the error information you provided, I found similar error information:

Phenomenon:
Executing show fields from a reports the following error

Error: Can't create/write to file '/tmp/#sql_419_0.MYI' (Errcode: 17 - File exists): SHOW FULL FIELDS FROM `a`

Solution:

In /tmp, remove the related #sql files.

Link: http://blog.itpub.net/25099483/viewspace-2133539/
You can refer to it.

| username: 会飞的土拨鼠 | Original post link

It is recommended to check the data files and log logs.

| username: system | Original post link

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