[Urgent Help Needed] TiKV Component Remains in Offline State After Scaling In/Out

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

Original topic: 【紧急求助】TIKV组件扩缩容后一直处于Offline状态

| username: TiDBer_70iA97nn

[TiDB Usage Environment] Production Environment
[TiDB Version] V7.5.0
[Reproduction Path] After scaling in and then scaling out on the same server, executed curl -X DELETE (referencing an expert’s column - Quickly Recover from TIKV Node Data File Deletion Without Replacing Server | TiDB Community)
[Encountered Issue: Phenomenon and Impact] Currently, there are a total of 4 stores. The store that was scaled in remains in the Offline state and has not been deleted. The tikv.log frequently shows two error logs, as shown in the images below.

[Attachments: Screenshots/Logs/Monitoring]