mirror of
https://github.com/kvcache-ai/Mooncake.git
synced 2026-11-05 01:17:55 +00:00
[GH-ISSUE #607] [Usage]: When using MooncakeDistributedStore in Python, after the written client is closed, other clients cannot query the written value #202
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#202
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 @hhwode on GitHub (Jul 9, 2025).
Original GitHub issue: https://github.com/kvcache-ai/Mooncake/issues/607
Describe your usage question
when using at node 1:
using in node 2:
It is right for store.put, at document https://github.com/kvcache-ai/Mooncake/blob/main/doc/en/mooncake-store-preview.md. The put operation will copy the replica to other client, but KV seems to only exist on the writing client, and it was deleted after being closed.
master service logs:
Before submitting a new issue...
@xiaguan commented on GitHub (Jul 9, 2025):
Right now in the Python bindings, we default the replica number to 1 and try to allocate memory form itself first.
I think this may clear up the confusion you had.
I'll submit a PR soon to add support for ReplicaConfig in the Python bindings.
@hhwode commented on GitHub (Jul 9, 2025):
Is there any other way to configure the number of replicas on the Python side,and the document states that it is possible to offload kv to disk through MOONCAKE-STORAGE-ROOT_DIR. Does Python not support this.
@xiaguan commented on GitHub (Jul 9, 2025):
https://github.com/kvcache-ai/Mooncake/pull/608, Python binding's replica config PR has been submitted—just waiting on review and merge.
As for offloading to disk: yes, the Python client does support this. You just need to set the appropriate environment variable. That said, this feature is still experimental for now, and it's mainly intended to serve as a read cache for the client itself. @SgtPepperr , could u help answer this?
@xiaguan commented on GitHub (Jul 10, 2025):
The PR has been merged, but we haven't published a new release yet. If you need it right away, you can build from main. Python now supports setting
ReplicateConfigdirectly when calling put() releated interface.@LuyuZhang00 commented on GitHub (Jul 10, 2025):
test-script:mooncake-store/tests/stress_cluster_benchmark.py
During concurrent execution of the test-script as role=prefill on node1 and role=decode on node2, the error 'Transfer failed for batch xxxxx task 0 with status 6' occurred, which is confusing. @xiaguan
@xiaguan commented on GitHub (Jul 10, 2025):
Could you share more detailed logs? And please checkout your config.
Status 6 means the transfer failed.
@LuyuZhang00 commented on GitHub (Jul 10, 2025):
example
E0710 09:48:23.776901 5615 store_py.cpp:1202] BatchGet failed for key 'key1199': TRANSFER_FAILparser.add_argument("--local-hostname", type=str, default="localhost", help="Local hostname")
in node1 :local-hostname is node 1 name,
in node2: I set node2, which localhost should set
@xiaguan commented on GitHub (Jul 10, 2025):
Is it possible that the prefill node exited during the data transfer? Since we're using the client's own memory for storage, that could explain it.
@hhwode commented on GitHub (Jul 11, 2025):
Thanks, i will try it.
@stmatengss commented on GitHub (Nov 25, 2025):
When any client is shut down, we should provide an option to migrate data.
@github-actions[bot] commented on GitHub (Jun 30, 2026):
This issue has had no activity for 90 days and will be closed in 7 days if there is no further activity. Please comment or react if it should stay open.
@github-actions[bot] commented on GitHub (Jul 7, 2026):
Closing due to 3 months of inactivity. If this is still relevant, please comment and we can reopen.