[
https://issues.apache.org/jira/browse/AURORA-898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14187098#comment-14187098
]
Bill Farner commented on AURORA-898:
------------------------------------
This sounds like a misbehaving executor (possibly a result of a misbehaving
client). The executor logs should contain clues, they will be contained in the
directory containing the sandbox, formatted as {{/var/lib/mesos/slaves/<slave
id>/frameworks/<framework id>/executors/thermos-<task id>/runs/latest/}}. All
the variable directories will likely tab complete, with the exception of the
task ID-based one. You can get the task ID by clicking the pi link in the
lower right corner of the same page where you grabbed the task state
transitions.
> 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)
