You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@falcon.apache.org by "Suhas Vasu (JIRA)" <ji...@apache.org> on 2014/11/24 11:23:12 UTC

[jira] [Resolved] (FALCON-912) Lineage recorder fails at createFileSystem()

     [ https://issues.apache.org/jira/browse/FALCON-912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Suhas Vasu resolved FALCON-912.
-------------------------------
    Resolution: Invalid
      Assignee: Suhas Vasu

Invalid bug

> Lineage recorder fails at createFileSystem()
> --------------------------------------------
>
>                 Key: FALCON-912
>                 URL: https://issues.apache.org/jira/browse/FALCON-912
>             Project: Falcon
>          Issue Type: Bug
>            Reporter: Suhas Vasu
>            Assignee: Suhas Vasu
>
> We recently had an instance where falcon post-processing was failing at LineageRecorder.
> The exact scenario was - the log retention was set to a very low period and as a result the logs directory in the staging directory for the process got deleted on hdfs as it was empty. So when the next instance ran, in the succeeded-postprocessing LineageRecorder tries creating directories on the hdfs in the staging directory for the particular process and it fails with incorrect permissions.
> {noformat}
> try {
>             return createFileSystem(UserGroupInformation.getLoginUser(), uri, conf);
>         } catch (IOException e) {
>             throw new FalconException("Exception while getting FileSystem for: " + uri, e);
>         }
> {noformat}
> The post processing runs as login user which is mapred but the owner of the staging directory is the owner specified in the feed/process.
> So it should be {{UserGroupInformation.getCurrentUser()}} rather than {{UserGroupInformation.getLoginUser()}}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)