[
https://issues.apache.org/jira/browse/OOZIE-1735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Satish Subhashrao Saley updated OOZIE-1735:
-------------------------------------------
Attachment: OOZIE-1735-Doc-V4.patch
[Oozie
documentation|https://oozie.apache.org/docs/4.2.0/DG_CoordinatorRerun.html#Pre-Conditions]
says
{quote}
Rerun coordinator action must be in TIMEDOUT/SUCCEEDED/KILLED/FAILED.
Coordinator actions cannot be rerun if the coordinator job is in the KILLED or
FAILED state.
{quote}
It's not true after the support for resuming of failed coordinator job and
rerun of a failed coordinator action was added.
Uploading documentation change patch.
> Support resuming of failed coordinator job and rerun of a failed coordinator
> action
> -----------------------------------------------------------------------------------
>
> Key: OOZIE-1735
> URL: https://issues.apache.org/jira/browse/OOZIE-1735
> Project: Oozie
> Issue Type: Bug
> Reporter: Purshotam Shah
> Assignee: Purshotam Shah
> Fix For: 4.1.0
>
> Attachments: OOZIE-1735-Doc-V4.patch, OOZIE-1735-V2.patch,
> OOZIE-1735-V2.patch, OOZIE-1735-V3.patch, OOZIE-1735_v1.patch
>
>
> We should support resuming of failed coordinator job. Job are set to failed
> if there are runtime error( like SQL timeout).
> In current scenario there is no way to recover beside running SQL.
> Resuming of failed coordinator job should also set pending to 1 ,reset
> doneMaterialization and last modified to current time. So that
> materialization continues.
> We should also provide an option of resuming failed action. The behavior will
> be same as killed option.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
