[
https://issues.apache.org/jira/browse/HDFS-11173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Cseh updated HDFS-11173:
------------------------------
Description:
We've encountered cases when the LauncherMapper stuck around after sending out
the notifications to Oozie. If the callback is processed before the external
job's status is updated to FINISHED, Oozie won't update the action's status for
10 minutes.
We could add a delayed check to
[CompletedAcitonXCommand|https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/command/wf/CompletedActionXCommand.java#120
] to avoid this.
was:
We've encountered cases when the LauncherMapper stuck around after sending out
the notifications to Oozie. If the callback is processed before the external
job's status is updated to FINISHED, Oozie won't update the action's status for
10 minutes.
We could add a delayed check to [CompletedAcitonXCommand |
https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/command/wf/CompletedActionXCommand.java#L120
] to avoid this.
> Reschedule CompletedActionXCommand if the job is not completed
> --------------------------------------------------------------
>
> Key: HDFS-11173
> URL: https://issues.apache.org/jira/browse/HDFS-11173
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Peter Cseh
>
> We've encountered cases when the LauncherMapper stuck around after sending
> out the notifications to Oozie. If the callback is processed before the
> external job's status is updated to FINISHED, Oozie won't update the action's
> status for 10 minutes.
> We could add a delayed check to
> [CompletedAcitonXCommand|https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/command/wf/CompletedActionXCommand.java#120
> ] to avoid this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
