You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@aurora.apache.org by "Jordan Ly (JIRA)" <ji...@apache.org> on 2017/05/30 21:22:04 UTC
[jira] [Commented] (AURORA-1928) Aurora should prioritize adding
instances over updating instances during an update
[ https://issues.apache.org/jira/browse/AURORA-1928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16030158#comment-16030158 ]
Jordan Ly commented on AURORA-1928:
-----------------------------------
Review out: https://reviews.apache.org/r/59640/
> Aurora should prioritize adding instances over updating instances during an update
> ----------------------------------------------------------------------------------
>
> Key: AURORA-1928
> URL: https://issues.apache.org/jira/browse/AURORA-1928
> Project: Aurora
> Issue Type: Task
> Components: Scheduler
> Reporter: Jordan Ly
> Assignee: Jordan Ly
> Priority: Minor
>
> Often times, when adding capacity to a service, I increase the number of instances and the batch_size that the updates roll out at.
> For the first deploy, this updates the old instances with the more aggressive batch size before the new instances are started.
> It might be better for Aurora to prioritize the "adding instances" step of upgrades.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)