mirror of
https://github.com/kvcache-ai/Mooncake.git
synced 2026-11-05 01:17:55 +00:00
[GH-ISSUE #3658] [Bug]: batch_get_session_start fails with 702 INVALID_REPLICA when SSD offloading is enabled #934
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#934
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?
Originally created by @Yong-ee on GitHub (Aug 25, 2026).
Original GitHub issue: https://github.com/kvcache-ai/Mooncake/issues/3658
Bug Report
Description
I deployed Mooncake master and client using the latest main branch, with SSD offloading enabled. When retrieving data via the Get Session API, I received error
702 (ErrorCode::INVALID_REPLICA). The logs show the following errors:Root Cause
When SSD offloading is enabled, some data resides on SSD instead of in‑memory.
The
batch_get_session_startmethod only selects memory replicas. As a result, keys whose replicas exist only on SSD will return error 702.Expected behavior
Similar to
batch_get_into, useSelectBestReplicato select the best replica for each key.Before submitting...
@github-actions[bot] commented on GitHub (Aug 25, 2026):
Thanks for opening this issue, @Yong-ee!
15357666A maintainer will triage this when possible. To help us respond faster, please include:
Useful links: Documentation · Contributing guide
@Yong-ee commented on GitHub (Aug 25, 2026):
cc @ascend-direct-dev
@Yong-ee commented on GitHub (Aug 25, 2026):
https://github.com/kvcache-ai/Mooncake/pull/3662 this PR,
batch_get_into_multi_buffer_rangesdoes not adapt to non‑memory replicas. Therefore, if a non‑memory replica is selected, get‑buffer operations will still encounter issues.