[
https://issues.apache.org/jira/browse/OOZIE-549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J reassigned OOZIE-549:
-----------------------------
Assignee: (was: Roman Shaposhnik)
> OOZIE-132: Kill commands in Oozie has to be executed with higher priority
> -------------------------------------------------------------------------
>
> Key: OOZIE-549
> URL: https://issues.apache.org/jira/browse/OOZIE-549
> Project: Oozie
> Issue Type: New Feature
> Reporter: Angelo K. Huang
>
> Kill commands for coordinator, workflow, and bundle all have same problems
> when system is high-loaded condition. When kill-command submits for one job,
> kill-command tries to acquire job's lock before moving job status to KILLED.
> If lock is not acquired, it requeues itself immediately. This also means
> kill-command could run forever and job is still not in killed state if lock
> is never successful.
> Oozie dev propose one solution is to add KILLING state to job level to mark
> job which has been ready to kill but other commands still have locks on job
> and there are commands of this job are in the Oozie queue. KILLING state
> means to freeze all activities on this job and notify new-coming commands not
> to enter into queue.
> Comments welcome.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
