mirror of
https://github.com/deepseek-ai/3FS.git
synced 2026-11-05 00:47:47 +00:00
[GH-ISSUE #344] StorageOperator::batchRead中,判断待读target是否upToDate时,是否有必要判断flat::PublicTargetState::SERVING #213
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
deepseek-ai/3FS#213
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 @kaede11 on GitHub (Sep 30, 2025).
Original GitHub issue: https://github.com/deepseek-ai/3FS/issues/344
storage节点failover后,local state达到UPTODATE后,会通过mgmtd广播public state(Serving)。
当前的upToDate实现如下所示:
`
bool upToDate() const {
}
`
查询请求到达已经是LocalTargetState::UPTODATE的storage时,会因为该storage节点还没收到mgmtd的广播,而拒绝请求,导致client侧延迟抖动。
由于client和storage获取routing info是有时间差的,所以upToDate中是否没必要再判断public state:
@SF-Zhou commented on GitHub (Oct 10, 2025):
确实是这样,我修复一下这个问题。