[
https://issues.apache.org/jira/browse/FALCON-221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Srikanth Sundarrajan updated FALCON-221:
----------------------------------------
Attachment: FALCON-221.patch
Have a patch to fallback to history logs in case job is retired out of job
tracker.
As [~svenkat] has suggested, we can piggy back on the default behavior of the
history server in Yarn to handle this for hadoop2.
[~shwethags], Aren't we doing workflow retries ? Coord retries to be done only
for timedout instances, in which case, there are logs for run-id 0 (barring
oozie logs).
> Logmover is not copying all action level logs
> ---------------------------------------------
>
> Key: FALCON-221
> URL: https://issues.apache.org/jira/browse/FALCON-221
> Project: Falcon
> Issue Type: Bug
> Components: archival
> Affects Versions: 0.3
> Reporter: Pracheer Agarwal
> Priority: Minor
> Attachments: FALCON-221.patch
>
>
> Log mover copies the action level logs and oozie logs of a worklfow to hdfs.
> My workflow has 6 actions. Logs of 2-3 actions are getting copied to hdfs.
> Logs for all the actions are not available at hdfs.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
