[
https://issues.apache.org/jira/browse/AURORA-898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14192734#comment-14192734
]
Bhuvan Arumugam commented on AURORA-898:
----------------------------------------
we using custom client. if you use new client built straight from master (as of
now) and run it against scheduler built as of 10/22, you could replicate this
bug.
if you build client against master as of 10/22 and run it against scheduler
built straight from master (as of now), you could replicate 1st issue described
in [#comment-14192533].
If you couldn't replicate this bug, sure, i will share this client privately.
> 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)
