falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shwetha G S (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-221) Logmover is not copying all action level logs
Date Wed, 29 Jan 2014 10:26:09 GMT

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

Shwetha G S commented on FALCON-221:

Currently, logpath contains runid. If a coord action is re-run, oozie creates new workflow.
So, runid is reset to 0 and the logs are over-written. Can the logpath contain timestamp as
against the runid?

> 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

View raw message