Setting permissions for cloudera hadoop

13,669

I solved my problem: In cloudera manager, go to hdfs configuration under advanced and put the following code in HDFS Service Configuration Safety Valve:

<property>
  <name>dfs.permissions</name>
  <value>false</value>
</property>
Share:
13,669
KarelV
Author by

KarelV

Updated on July 19, 2022

Comments

  • KarelV
    KarelV almost 2 years

    I installed coudera hadoop 4 on a cluster of about 20 nodes. Using cloudera manager it went really smooth and all, but when I want to create an input directory using hadoop fs -mkdir input I get the following error: mkdir: Permission denied: user=root, access=WRITE, inode="/user":hdfs:supergroup:drwxr-xr-x Looks like a classic wrong permissions case but I have no clue where to start to fix this. I found this document which I think would solve my problem if I knew what to do with it. For starters I don't know whether I am using MapReduce v1 of v2 (I don't see any yarn service in my cloudera manager so my guess would be v1 (?)). Second, since the whole installation was automatic I don't know what is installed and where.

    Could anyone point me towards some easy steps to solve my problem? I'm really looking for the easiest solution here, I don't care at all about security since it is only a test. If I could give all users all possible permissions that would be fine.

  • Shehaaz
    Shehaaz almost 11 years
    Thank you! Now That needs to be set in the GUI. localhost:7180 -> hdfs1 -> Configuration -> View and Edit -> Uncheck "Check HDFS Persmissions". Restart VM.
  • iRuth
    iRuth over 10 years
    Thanks for saving me a lot of time!
  • sandeepkunkunuru
    sandeepkunkunuru about 10 years
    alternatively this works "sudo -u hdfs hadoop fs -mkdir input"
  • user3123372
    user3123372 almost 8 years
    hdfs user doesnt have a password in this case and not in the sudoers list u need to add it to sudoers list , first , and u will need the password for that
  • Jeremy Hajek
    Jeremy Hajek about 7 years
    This does solve the issue - but is turning off permissions a "nuclear" solution? Much like turning off the firewall -- it doesn't actually solve the problem?