[jira] [Commented] (AURORA-1258) Improve procedure for adding instances to a job

["Joe Smith (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AURORA-1258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14484698#comment-14484698 ] 

Joe Smith commented on AURORA-1258:
-----------------------------------

Here's a link to [the related mailing list conversation on the dev@ list|http://mail-archives.apache.org/mod_mbox/incubator-aurora-dev/201504.mbox/%3cCAAATh-Yu+m6jUBQ0iuinGVwB7vryRj0wi92ME_0Fkv+Pn0_Qrw@mail.gmail.com%3e].

> Improve procedure for adding instances to a job
> -----------------------------------------------
>
>                 Key: AURORA-1258
>                 URL: https://issues.apache.org/jira/browse/AURORA-1258
>             Project: Aurora
>          Issue Type: Story
>          Components: Reliability, Usability
>            Reporter: Joe Smith
>
> The current process for adding instances to a job is highly manual, and potentially dangerous.
> 1. Take a config for a job with 10 instances, update it to 20 instances.
> 2. The batch size will be increased, and users will need to specify shards 10 to 19.
> 3. After this update is complete, users will need to manually update shards 0-9 again.
> There may be other changes pulled in as part of this update other than just increasing the number of instances, which could further complicate things.
> One possible improvement would be to change the updater from 'under-provision' where it kills instances first, then schedules new instances, to an 'over-provision' where it adds on new instances, then backpedals and kills the old instances.
> Overall, a single command or process for a user to take an already-existing job and increase the number of instances would reduce overhead and fat-fingering.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)