Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]
Created 12-11-2015 09:36 PM
Hi,
We are using falcon-0.6.
I am trying to submit Falcon feed schedule as user1 but it throws below error
Permission denied: user=user1, access=WRITE, inode="/apps/falcon/backupCluster/staging/falcon/workflows/feed":falcon:hdfs:drwxr-xr-x
I gave 777 permissions to staging directory but I still see the same error.
I am able to submit the schedule as falcon user but could not as any other user.
Please help me with this
Thanks,
Venkat
Created 12-11-2015 09:52 PM
This is a known bug in Falcon and was recently fixed in FALCON-1647 (https://issues.apache.org/jira/browse/FALCON-1647). To fixed your issue, please gave 777 permission to the following two directories: /apps/falcon/backupCluster/staging/falcon/workflows/feed and /apps/falcon/backupCluster/staging/falcon/workflows/process. Otherwise, it only allows the first user to submit entities. Thanks.
Created 12-18-2015 03:58 PM
I think the problems is, though I gave 777 over /apps/falcon/backupCluster/staging, when I tried creating directory under /apps/falcon/backupCluster/staging/falcon/workflows/feed as falcon user, it is created with 755 permissions as below
[falcon@hostname ~]$ hdfs dfs -mkdir /apps/falcon/backupCluster/staging/falcon/workflows/feed/test1
hdfs dfs -ls /apps/falcon/backupCluster/staging/falcon/workflows/feed
drwxr-xr-x - falcon hdfs 0 2015-12-18 09:55 /apps/falcon/backupCluster/staging/falcon/workflows/feed/test1
The directory is not created with 777 permission (umask 022).
Do you think it could be the reason?
Created 12-18-2015 04:39 PM
Yes. That is correct.