Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.
Original topic: tikv宕机后重启
[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]
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.
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~
Let’s talk about how the previous issues were handled.
What caused the crash? Where are the complete logs?
Is the error that the disk file cannot be found? Is the disk damaged?
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.
It is recommended to check the data files and log logs.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.