aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maxim Khutornenko (JIRA)" <>
Subject [jira] [Updated] (AURORA-83) Killing a job attempts to transition non-active tasks
Date Mon, 26 Jan 2015 22:59:43 GMT


Maxim Khutornenko updated AURORA-83:
    Fix Version/s: 0.7.0

> Killing a job attempts to transition non-active tasks
> -----------------------------------------------------
>                 Key: AURORA-83
>                 URL:
>             Project: Aurora
>          Issue Type: Bug
>          Components: Client, Scheduler
>            Reporter: Bill Farner
>            Priority: Minor
>              Labels: O3
>             Fix For: 0.7.0
> The client exposes a {{kill}} subcommand to kill jobs, which currently applies to cron
and non-cron jobs.  This is translated into a {{killTasks}} RPC, and the scheduler internally
inspects the query to determine if this is a request to kill a whole job.  Acting on this
RPC for a job means that the scheduler attempts to transition a slew of tasks to {{KILLING}}
state.  This is benign, but inefficient and can result in lots of log noise.
> In the short term, the scheduler should restrict non-cron job-scoped kills to only active
tasks.  Longer-term, we should expose a more explicit way for the client to ask for a cron
job to be unscheduled.

This message was sent by Atlassian JIRA

View raw message