[
https://issues.apache.org/jira/browse/AURORA-898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14195178#comment-14195178
]
Bhuvan Arumugam commented on AURORA-898:
----------------------------------------
[~maximk] i confirmed i couldn't replicate it without our local modifications.
latest scheduler and 10/22 client
latest client and 10/22 scheduler
yes, we have modified thrift protocol {{api.thrift}} to support Docker based
jobs. We were earlier using key {{28}}, for {{TaskConfig.ContainerConfig}}. The
{{TaskConfig.JobKey}} also use {{28}}, we changed it to {{29}} and it mean we
MUST ship new client to our users.
Thank you for taking time to replicate it. We appreciate it!
> 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)
