[
https://issues.apache.org/jira/browse/AURORA-898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14190560#comment-14190560
]
Bhuvan Arumugam commented on AURORA-898:
----------------------------------------
i couldn't replicate this bug with latest scheduler built as of
https://github.com/apache/incubator-aurora/commit/d85e616b3b930b4a3e55e362d13c98e51069145d.
Presumably, one of following commits fixed it:
{code}
a518053 Adding missing JobConfiguration backfill for task config job field.
88bc2f2 Fixing transient error message formatting in scheduler_client.py
a675213 Fixing error reporting in v1 client updater.
9fb2ce4 Make job key backfilling more robust.
{code}
Using new client I couldn't replicate it with scheduler which has above fixes.
Using new client I could replicate it with scheduler which doesn't have above
fixes.
> 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)
