[
https://issues.apache.org/jira/browse/AURORA-932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14215308#comment-14215308
]
Joshua Cohen commented on AURORA-932:
-------------------------------------
What's the expected workflow when creating a job in a batch?
{{aurora job create cluster/role/env/job/1-20}} to create the first 20
instances. Do you then come back and do {{aurora job create
cluster/role/env/job/21-40}} for the next batch? This seems like it raises a
few usability concerns (e.g. what if you specify a range that includes some
instances that have already been created? What if you skip a range in the
middle? Also, what happens if you go to update, restart, kill, etc. before
fully creating all instances? If you omit the instances will the scheduler need
to know that even though the config calls for 40, 60, whatever instances, only
20 have actually been created (probably it already does know, but today it
doesn't need to check unless an instance range is specified).
> Aurora job create should support batchsize
> ------------------------------------------
>
> Key: AURORA-932
> URL: https://issues.apache.org/jira/browse/AURORA-932
> Project: Aurora
> Issue Type: Task
> Components: Client
> Reporter: Maxim Khutornenko
>
> The {{aurora job create}} command should support batching of tasks. This will
> be a welcome feature for the users when dealing with large jobs as well as a
> perf improvement for the scheduler UI (e.g.: AURORA-522) and will be
> consistent with other client commands already supporting batchsize, like
> update, restart, kill, killall (AURORA-283).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
