[
https://issues.apache.org/jira/browse/AURORA-898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14192578#comment-14192578
]
Maxim Khutornenko commented on AURORA-898:
------------------------------------------
[~bhuvan], I tried in vagrant with both client v1 and v2 as of
a5862ae94d4d6f31a4086a8d22ae150b12de9509 and could not reproduce the behavior
you describe. Does your deployed scheduler version have patches for this ticket
and the AURORA-899? How old is your client?
The fact that your request has {{JobKey(role:null, environment:null,
name:null)}} is suspicious as any pre-AURORA-84 client should result in a null
jobKey as its schema would not know anything about the new field, e.g.:
{noformat}
I1031 21:48:49.621 THREAD118
org.apache.aurora.scheduler.thrift.aop.LoggingInterceptor.invoke:
createJob(JobConfiguration(key:JobKey(role:www-data, environment:prod, name:he
llo), owner:Identity(role:www-data, user:vagrant), cronSchedule:null,
cronCollisionPolicy:KILL_EXISTING, taskConfig:TaskConfig(job:null,
owner:Identity(role:www-data, user:v
agrant), environment:prod, jobName:hello, isService:true, numCpus:1.0,
ramMb:128, diskMb:128, priority:0, maxTaskFailures:1, production:false,
constraints:[], requestedPorts
:[], taskLinks:{}, executorConfig:ExecutorConfig(name:BLANKED, data:BLANKED),
metadata:[]), instanceCount:1), null, SessionKey(mechanism:UNAUTHENTICATED,
data:50 D0 14 4C 71 0D 4C 80 80 4C 40))
{noformat}
> unable to kill a job that is in ASSIGNED state
> ----------------------------------------------
>
> Key: AURORA-898
> URL: https://issues.apache.org/jira/browse/AURORA-898
> Project: Aurora
> Issue Type: Bug
> Components: Scheduler
> Affects Versions: 0.5.0
> Reporter: Bhuvan Arumugam
>
> we unable to kill a job that's in ASSIGNED state. it's always reproducible,
> even with a hello world job.
> The {{aurora killall}} command give up after 5mins with this message:
> {code}
> .
> .
> DEBUG "POST /api HTTP/1.1" 200 None
> DEBUG] "POST /api HTTP/1.1" 200 None
> DEBUG] handle_response(): returning <Response [200]>
> DEBUG] Response from scheduler: OK (message: None)
> FATAL] Tasks were not killed in time.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
