kvcache-ai / kvcache-ai/Mooncake
[Bug]: mooncake-store offload SSD some question
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 6.6k
- Forks
- 1.2k
- Avg merge
- 3d 5h
- Merged PRs (30d)
- 312
Description
Bug Report
When SSD offload is enabled, I noticed that after writing some keys on Node 1, they get offloaded to the SSD. Later, when I try to read these keys from Node 2, if the key has already been evicted from Node 1’s DRAM but still resides on its SSD, Node 2 will attempt to fetch it. However, Node 2 tries to read directly via the local SSD file path of the key. Since Node 2 obviously does not have this file locally, the read operation fails.
Before submitting...
- Ensure you searched for relevant issues and read the [documentation]
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the mooncake-store SSD offload read path, focusing on how Node 2 handles a key that was evicted from Node 1's DRAM but remains on Node 1's SSD. Reproduce the Node 1/Node 2 scenario described in the report and identify where the remote read uses a local SSD path. Done means the key can be fetched successfully from its owning node's SSD.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100