[
https://issues.apache.org/jira/browse/OOZIE-3037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ergin Demirel updated OOZIE-3037:
---------------------------------
Description:
Oozie is not delivering killed status to the oozie.wf.workflow.notification.url
or oozie.coord.workflow.notification.ur webhook when it's killed via kill
command. I am able to capture all statuses if the workflow complete or fails
naturally however calling kill command on workflow / coordinator will left
status in RUNNING state rather than KILLED. I am not sure if this is by design.
IMHO expected behavior should be reporting KILLED status and then killing the
job.
was:Oozie is not delivering killed status to the
oozie.wf.workflow.notification.url or oozie.coord.workflow.notification.ur
webhook when it's killed via kill command. I am able to capture all statuses
if the workflow complete or fails naturally however calling kill command on
workflow / coordinator will left status in RUNNING state rather than KILLED. I
am not sure if this is by design.
> Oozie fails to deliver notification status when it's killed
> -----------------------------------------------------------
>
> Key: OOZIE-3037
> URL: https://issues.apache.org/jira/browse/OOZIE-3037
> Project: Oozie
> Issue Type: Bug
> Environment: Server version [4.1.0-cdh5.5.2]
> Reporter: Ergin Demirel
>
> Oozie is not delivering killed status to the
> oozie.wf.workflow.notification.url or oozie.coord.workflow.notification.ur
> webhook when it's killed via kill command. I am able to capture all statuses
> if the workflow complete or fails naturally however calling kill command on
> workflow / coordinator will left status in RUNNING state rather than KILLED.
> I am not sure if this is by design. IMHO expected behavior should be
> reporting KILLED status and then killing the job.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
