Old TorchServe workers remain active after new model version registration
Goal: Ensure that when a new model version is registered in TorchServe, workers serving the previous version terminate automatically after all in‑flight requests finish, enabling a seamless cutover without manual intervention. Constraints: The version_policy feature does not automatically drain old workers; they continue to handle existing requests until com
pytorch