falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Srikanth Sundarrajan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-221) Logmover is not copying all action level logs
Date Thu, 30 Jan 2014 05:26:12 GMT

    [ https://issues.apache.org/jira/browse/FALCON-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13886266#comment-13886266
] 

Srikanth Sundarrajan commented on FALCON-221:
---------------------------------------------

There is an implicit assumption that run-id is monotonically increasing and starts from 0.
This is used by retries to figure if we have reached max attempts and also instance log command
uses the run id to figure the latest logs and show only the latest logs by default. We can
strictly work based on what Falcon contracts are.

> 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
>            Assignee: Srikanth Sundarrajan
>            Priority: Minor
>             Fix For: 0.5
>
>         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)

Mime
View raw message