Lotus Hotstore Badger GC

[ZenGround0]

Checklist

• This is not a new feature or an enhancement to the Filecoin protocol. If it is, please open an FIP issue.
• This is not brainstorming ideas. If you have an idea you'd like to discuss, please open a new discussion on the lotus forum and select the category as Ideas.
• I have a specific, actionable, and well motivated feature request to propose.

Lotus component

• lotus daemon - chain sync
• lotus miner - mining and block production
• lotus miner/worker - sealing
• lotus miner - proving(WindowPoSt)
• lotus miner/market - storage deal
• lotus miner/market - retrieval deal
• lotus miner/market - data transfer
• lotus client
• lotus JSON-RPC API
• lotus message management (mpool)
• Other

What is the motivation behind this feature request? Is your feature request related to a problem? Please describe.

While investigating splitstore its become clear that lots of hotstore bloat comes in the form of non-GCed dead badger state. Moving GC will handle this but at large disk overhead. During normal operation it will likely make sense to run online GC of the hotstore at low thresholds to catch up on large amounts of state bloat.

Describe the solution you'd like

Cmd line tool for running badger gc

Describe alternatives you've considered

No response

Additional context

Ideally this solution will allow for incremental GCOnce badger GC or periodic run through vlog until no rewrites GC as happens today after online compactions