mirror of
https://github.com/kvcache-ai/Mooncake.git
synced 2026-11-05 01:17:55 +00:00
[PR #337] [MERGED] fix(store): the metadata leak after umount segment #1490
Labels
No labels
ascend
auto-closed
bug
bug
CI/Build
Common
documentation
enhancement
feature request
good first issue
help wanted
high priority
MetaX
nightly-failure
pull-request
PyTorch Backend
question
RFC
Roadmap
stale
Store
Tests
Transfer Engine
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
kvcache-ai/Mooncake#1490
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/kvcache-ai/Mooncake/pull/337
Author: @maobaolong
Created: 5/8/2025
Status: ✅ Merged
Merged: 5/15/2025
Merged by: @stmatengss
Base:
main← Head:fixUnmountLeak📝 Commits (2)
b85e278fix the metadata leak after umount segment5d4c261Add a performance test📊 Changes
3 files changed (+173 additions, -1 deletions)
View changed files
📝
mooncake-store/include/master_service.h(+6 -0)📝
mooncake-store/src/master_service.cpp(+38 -1)📝
mooncake-store/tests/master_service_test.cpp(+129 -0)📄 Description
Description
Although
UnmountSegementremove the specified segment from buffer_allocator_manager, but the related metadata of objects still exists.Although
MetadataAccessorwill remove these invalid key in the constructor, but it will still leak if the related keys do not be accessed any more.So the safe way is remove the related keys in the UnmountSegement function.
Future work
UnmountSegementrequest and execute it async.🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.