Maxim Khutornenko created AURORA-996:
----------------------------------------
Summary: Aurora client batch job kill does not filter active tasks
Key: AURORA-996
URL: https://issues.apache.org/jira/browse/AURORA-996
Project: Aurora
Issue Type: Bug
Components: Client
Reporter: Maxim Khutornenko
Priority: Blocker
Aurora client batched kill does not filter for active tasks and attempts to
kill any unique instance IDs it can find (including completed tasks):
For example, a job kill that does not exist any longer but used to have 4
instances:
{noformat}
vagrant@vagrant-ubuntu-trusty-64:~$ aurora job killall
devcluster/www-data/prod/hello
INFO] Checking status of devcluster/www-data/prod/hello
INFO]
INFO] Killing tasks for job: devcluster/www-data/prod/hello
INFO] Instances to be killed: [0]
INFO] No tasks to kill.
Successfully killed instances [0]
INFO] Killing tasks for job: devcluster/www-data/prod/hello
INFO] Instances to be killed: [1]
INFO] No tasks to kill.
Successfully killed instances [1]
INFO] Killing tasks for job: devcluster/www-data/prod/hello
INFO] Instances to be killed: [2]
INFO] No tasks to kill.
Successfully killed instances [2]
INFO] Killing tasks for job: devcluster/www-data/prod/hello
INFO] Instances to be killed: [3]
INFO] No tasks to kill.
Successfully killed instances [3]
INFO] Killing tasks for job: devcluster/www-data/prod/hello
INFO] Instances to be killed: [4]
INFO] No tasks to kill.
Successfully killed instances [4]
Job killall succeeded
{noformat}
Checking history it appears that this bug has been in place since inception.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
