[
https://issues.apache.org/jira/browse/OOZIE-1929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Bukatovic updated OOZIE-1929:
------------------------------------
Labels: hcfs (was: )
> oozie jobs don't run on hcfs
> ----------------------------
>
> Key: OOZIE-1929
> URL: https://issues.apache.org/jira/browse/OOZIE-1929
> Project: Oozie
> Issue Type: Bug
> Affects Versions: 4.0.0
> Environment: Red Hat Enterprise Linux Server release 6.5 (Santiago)
> Linux dhcp-lab-151.englab.brq.redhat.com 2.6.32-431.20.3.el6.x86_64 #1 SMP
> Fri Jun 6 18:30:54 EDT 2014 x86_64 x86_64 x86_64 GNU/Linux
> hadoop-2.2.0.2.0.6.0-101.el6.x86_64
> hadoop-client-2.2.0.2.0.6.0-101.el6.x86_64
> hadoop-hdfs-2.2.0.2.0.6.0-101.el6.x86_64
> hadoop-libhdfs-2.2.0.2.0.6.0-101.el6.x86_64
> hadoop-lzo-0.5.0-1.x86_64
> hadoop-lzo-native-0.5.0-1.x86_64
> hadoop-mapreduce-2.2.0.2.0.6.0-101.el6.x86_64
> hadoop-yarn-2.2.0.2.0.6.0-101.el6.x86_64
> hadoop-yarn-nodemanager-2.2.0.2.0.6.0-101.el6.x86_64
> hadoop-yarn-resourcemanager-2.2.0.2.0.6.0-101.el6.x86_64
> oozie-client-4.0.0.2.0.6.0-101.el6.noarch
> Reporter: Martin Kudlej
> Labels: hcfs
>
> I've tried oozie examples with GlusterFS as HCFS. If I run job under user
> oozie it works. If I run job under different user it doesn't work.
> I run job under user user1, he has root rights for everything in
> sudoers(because oozie switch user accounts in time of job processing) and
> then oozie creates directory ".staging" which has these permissions:
> oozie hadoop rwx------
> Users user1 and oozie are members of hadoop group. That's ok. Problem is that
> oozie changes permissions of this directory in time so it is accesible just
> for oozie. Even if I change permisions to:
> oozie hadoop rwxrwx---
> oozie changes it back.
> In HDFS it works differently because oozie is in Supergroup.
> I think this should be fixed in oozie and it has these solutions(and maybe
> many more):
> 1) oozie will create this directory(or file and every other) with rights
> "rwx" for group
> 2) if job starts by user1 then oozie doesn't do sudo t oozie, so directory
> and files are made with proper permissions
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
