Mailing-List: contact dev-help@falcon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@falcon.apache.org
Date: Mon, 7 Dec 2015 19:22:11 +0000 (UTC)
From: "Balu Vellanki (JIRA)" <jira@apache.org>
To: dev@falcon.incubator.apache.org
Message-ID: <JIRA.12917765.1449094577000.292880.1449516131286@Atlassian.JIRA>
In-Reply-To: <JIRA.12917765.1449094577000@Atlassian.JIRA>
References: <JIRA.12917765.1449094577000@Atlassian.JIRA>
 <JIRA.12917765.1449094577506@arcas>
Subject: [jira] [Commented] (FALCON-1647) Unable to create feed :
 FilePermission error under cluster staging directory
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Balu Vellanki commented on FALCON-1647:
---------------------------------------

[~pallavi.rao] I agree with you that 777 should not be used as much as possible. I also agree that we should make this a separate Jira and unblock the current issue.  [~peeyushb] : If you agree, I will go ahead and commit the current patch after incorporating [~yzheng-hortonworks]'s recommendations. Please let me know.

> Unable to create feed : FilePermission error under cluster staging directory
> ----------------------------------------------------------------------------
>
>                 Key: FALCON-1647
>                 URL: https://issues.apache.org/jira/browse/FALCON-1647
>             Project: Falcon
>          Issue Type: Bug
>          Components: feed
>    Affects Versions: 0.8
>            Reporter: Balu Vellanki
>            Assignee: Balu Vellanki
>             Fix For: 0.9
>
>         Attachments: FALCON-1647.patch
>
>
> Submit a cluster entity as user "user1", schedule a feed entity as "user1".  Now submit and schedule a feed entity as "user2" and feed submission can fail with  the following error 
> {code}
> Caused by: org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.security.AccessControlException): Permission denied: user=user2, access=WRITE, inode="/apps/falcon-user1/staging/falcon/workflows/feed":user1:falcon:drwxr-xr-x
>    at org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.checkFsPermission(FSPermissionChecker.java:271)
>    at org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.check(FSPermissionChecker.java:257)
>    at org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.check(FSPermissionChecker.java:238)
> {code}
> This is caused because Falcon creates <staging_dir>/falcon/workflows/feed and <staging_dir>/falcon/workflows/process only when a feed/process entity are scheduled. The owner of these dirs is the user scheduling the entity. The permissions are based on the default umask of the FS.  If a new feed/process entity are being scheduled by a different user, things can fail.
> Solution is to make <staging_dir>/falcon/workflows/feed and <staging_dir>/falcon/workflows/process  owned by Falcon with permissions 777. 


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