[
https://issues.apache.org/jira/browse/FALCON-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13838830#comment-13838830
]
Shwetha G S commented on FALCON-221:
------------------------------------
2013-12-04 10:29:12,767 INFO - Ignoring hadoop TT log for non-pig and non-java
action::start: (LogMover:110)
2013-12-04 10:29:12,856 WARN - No running job for job id:
job_201311231404_735742 (LogMover:205)
2013-12-04 10:29:12,858 WARN - No running job for job id:
job_201311231404_735770 (LogMover:205)
2013-12-04 10:29:12,861 WARN - No running job for job id:
job_201311231404_737193 (LogMover:205)
2013-12-04 10:29:12,864 WARN - No running job for job id:
job_201311231404_737951 (LogMover:205)
2013-12-04 10:29:12,873 WARN - No running task for job:
job_201311231404_737992 (LogMover:214)
Looks like the job logs are moved out of JT to history when post-processing was
called
> 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
>
> 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#6144)
