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
Currently, when altering the replica_policy, update runs a pseudo blue-green deployment in the sense it launches all new resources.
Preferably, if only the replica_policy is changing, it alters the policy itself without deploying /tearing down new instances unless required by the new policy.
Example 1:
Init: Currently, 2 resources are running, but the min_replica is set to 3.
Result: Only 1 instance is launched.
Example 2:
Init: Currently, 2 resources are running, but the min_replica is set to 1 and qps would not be met if scaled down.
Result: 1 instance is torn down.
Solution Options:
Have update check to make sure only the replica_info has changed with a hash.
Use a flag with update that allows altering just the replica policy
Have a separate update endpoint which allows updating the replica policy.
Version & Commit info:
skypilot, version 0.7.0
skypilot, commit 3f62588
The text was updated successfully, but these errors were encountered:
Currently, when altering the
replica_policy
, update runs a pseudo blue-green deployment in the sense it launches all new resources.Preferably, if only the replica_policy is changing, it alters the policy itself without deploying /tearing down new instances unless required by the new policy.
Example 1:
Init: Currently, 2 resources are running, but the
min_replica
is set to 3.Result: Only 1 instance is launched.
Example 2:
Init: Currently, 2 resources are running, but the
min_replica
is set to 1 and qps would not be met if scaled down.Result: 1 instance is torn down.
Solution Options:
Version & Commit info:
skypilot, version 0.7.0
skypilot, commit 3f62588
The text was updated successfully, but these errors were encountered: