You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Originally, kvcache pod and vllm-engine pods were scheduled at the same node by the PodAffinity in kvcache crd.
However, after restarting llama-3-8b-instruct, kv cache pod and engine pod are scheduled in different pods. The new engine pod is scheduled in the new node but kv cache pod stays in the same pod.
Not sure which way is the best to make kv cache pod and engine pod colocated.
🐛 Describe the bug
Originally, kvcache pod and vllm-engine pods were scheduled at the same node by the PodAffinity in kvcache crd.
However, after restarting llama-3-8b-instruct, kv cache pod and engine pod are scheduled in different pods. The new engine pod is scheduled in the new node but kv cache pod stays in the same pod.
Not sure which way is the best to make kv cache pod and engine pod colocated.
Steps to Reproduce
Expected behavior
kv cache pod and engine are in the same node even after restarting engine pod.
Environment
main branch
The text was updated successfully, but these errors were encountered: