aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bhuvan Arumugam (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AURORA-898) unable to kill a job that is in ASSIGNED state
Date Tue, 28 Oct 2014 01:29:33 GMT

    [ https://issues.apache.org/jira/browse/AURORA-898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14186183#comment-14186183
] 

Bhuvan Arumugam commented on AURORA-898:
----------------------------------------

why is the job in ASSIGNED state for long? it's a client thingy. Jobs created using newer
client, built since 10/22, never get to RUNNING state. It stays in ASSIGNED state forever.

The issue don't occur with the client built using commit: 4ea8dd9ffd40a51ea89ee163003b6840b5b02626.

Commit delta that might have caused this problem:
https://github.com/apache/incubator-aurora/compare/4ea8dd9ffd40a51ea89ee163003b6840b5b02626...3778330cd37bc8b96907654b496c15152dfecea7

> 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)

Mime
View raw message