[
https://issues.apache.org/jira/browse/OOZIE-2623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15402748#comment-15402748
]
Rohini Palaniswamy commented on OOZIE-2623:
-------------------------------------------
Comments
- isRecoverySupported should be overridden and should return true similar
to FileOutputCommitter. This will ensure that if uber AM crashed right after
task completed successfully then the new AM attempt will not rerun the launcher
again and just continue to completion. We have encountered this scenario once
or twice. The recoverTask implementation can be empty as there is nothing to
recover.
- Check formatting in OozieLauncherOutputCommitter . Why is that method
names are arg0 instead of taskContext?
> Oozie should use a dummy OutputFormat
> -------------------------------------
>
> Key: OOZIE-2623
> URL: https://issues.apache.org/jira/browse/OOZIE-2623
> Project: Oozie
> Issue Type: Bug
> Reporter: Satish Subhashrao Saley
> Assignee: Satish Subhashrao Saley
> Attachments: OOZIE-2623-1.patch, OOZIE-2623-2.patch
>
>
> After fixing OOZIE-2475, killed actions have this exception.
> {code}
> 2016-06-13 20:49:46,068 [uber-SubtaskRunner] WARN
> org.apache.hadoop.mapred.LocalContainerLauncher - Exception running local
> (uberized) 'child' :
> org.apache.hadoop.ipc.RemoteException(java.io.FileNotFoundException): Invalid
> inode path:
> /user/rohinip/oozie_LL/0266574-160613173929807-oozie_LL-W/pig1--pig/output/_temporary/1/_temporary/attempt_1464982500298_46637_m_000000_0/part-00000
> (id=316134636)
> {code}
> This is because it currently uses FileOuputFormat and sets output directory
> to <actiondir>/output which is unnecessary.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
