[jira] [Commented] (OOZIE-2057) Unable to kill waiting coordinator

["Andrew Mains (JIRA)" <ji...@apache.org>]

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

Andrew Mains commented on OOZIE-2057:
-------------------------------------

I've been running into this same issue; oozie job -kill returns successfully and logs seems to indicate that the job is killed, but the job continues to be considered RUNNING by the UI and oozie jobs. All coordinator materializations are in waiting Logs:

{code}
2015-06-02 05:07:22,177  INFO CoordinatorEngine:541 - SERVER[master.local] USER[-] GROUP[-] TOKEN[-] APP[-] JOB[-] ACTION[-] User ? killed the Coordinator job 0000001-150602035522164-oozie-oozi-C
{code}

I don't have security on, so there shouldn't be a permissioning issue, like I've seen elsewhere. I'm also using mysql, not derby, so I don't think it's related to something like: http://stackoverflow.com/questions/18979204/can-not-kill-oozie-job-by-kill-command. Let me know if there's other information I can provide, or whether my issue should be considered a separate ticket.

> Unable to kill waiting coordinator
> ----------------------------------
>
>                 Key: OOZIE-2057
>                 URL: https://issues.apache.org/jira/browse/OOZIE-2057
>             Project: Oozie
>          Issue Type: Bug
>         Environment: Prod/Dev
>            Reporter: Praveen Adlakha
>
> Hi Team,
> If by mistake we create a wrong job that goes into waiting status I am not able to kill it.
> Please do something.
> Thanks
> Praveen



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)