[
https://issues.apache.org/jira/browse/AURORA-356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13980917#comment-13980917
]
Mark Chu-Carroll commented on AURORA-356:
-----------------------------------------
Safety.
Right now, if users issue a kill command with an error in it, it's an
all-or-nothing proposition; they can end up killing tons of stuff that they
didn't want to. Batching it gives them a chance to notice what's going on
before too many things get killed.
We discussed this back when we added this to the v2 client implementations
of the commands; this is just bringing v1 into parity during the transition
period between the clients.
-Mark
--
Mark Craig Chu-Carroll
*** Software Engineer@Twitter, Software Tools/Programming Language/Math Geek
*** Email:[email protected] / [email protected]
*** Blog: http://scientopia.org/blogs/goodmath
> Add batchsize to clientv1 implementations of kill & killall
> -----------------------------------------------------------
>
> Key: AURORA-356
> URL: https://issues.apache.org/jira/browse/AURORA-356
> Project: Aurora
> Issue Type: Task
> Components: Client
> Reporter: Mark Chu-Carroll
> Assignee: Mark Chu-Carroll
>
> For clientv2, we added batch oriented implementations of kill and killall, to
> match the existing batching functionality of restart and update.
> (AURORA-283). We should have the same batch options for legacy users of
> clientv1.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
