fix: preserve worker cache across duplicate index events - #802
Merged
Merged
Conversation
|
🎉 This PR is included in version 2.17.17 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
标题：修复 v1/v2 GPU index 兼容及 PodCache 冲突恢复
内容：
背景
v1/v2 混合运行或升级回滚期间，legacy
tensor-fusion.ai/index与 v2index_*资源并存。PodCache 在重复 index、删除事件乱序时可能覆盖或误删其他 worker 的缓存，导致 device-plugin 分配等待或绑定错误。修改内容
tensor-fusion.ai/index资源。index_*资源。验证
make testmake lintgo test ./pkg/hypervisor/backend/kubernetes