What should I do if RaftDB mistakenly enabled Titan and found that blob files are not being reclaimed?

Translated
1

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

Original topic: RaftDB误开了titan,发现blob文件不回收，请问怎么处理?

| username: kuiper

[TiKV Usage Environment] Production Environment
[TiKV Version] 5.3.1
[Encountered Problem] raftdb was mistakenly configured to enable titan, but it was found that its blob files are not being reclaimed, causing continuous space growth.
[Reproduction Path] What operations were performed to cause the problem
[Problem Phenomenon and Impact]
raftdb was mistakenly configured to enable titan, but it was found that its blob files are not being reclaimed, causing continuous space growth.
Even changing the garbage collection ratio of titan from 0.5 to 0.1 does not take effect. How should this be handled?

2
| username: xfworld | Original post link

For a production environment, it is not recommended to operate this way. It is suggested to stop the service, use BR for backup, and then restore it in a newly created cluster…

3
| username: kuiper | Original post link

Thank you for your reply~

4
| username: system | Original post link

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