Member since
02-22-2016
8
Posts
1
Kudos Received
1
Solution
My Accepted Solutions
Title | Views | Posted |
---|---|---|
5611 | 05-04-2020 05:34 AM |
10-21-2020
03:05 AM
Hello! The maven artifacts list for 7.1.3 is available at : https://docs.cloudera.com/cdp-private-cloud/latest/release-guide/topics/cdppvc-runtime-maven-7.1.3.html Is the same list for 7.1.4 available? Is it the same list? I am unable to find this list for CDP 7.1.4. Thanks.
... View more
Labels:
05-04-2020
05:34 AM
1 Kudo
Hi, Mondi! The msg you are getting is telling that user devuser does not have permission to write to the root (/) HDFS folder. This is normal, and just like a Linux FS. If you create a folder in HDFS and make your local unix account the owner, you can use that folder as you. If you want to create objects in hdfs /, you need to become the superuser, hdfs. Example: # create your folder
$ sudo -u hdfs hdfs dfs -mkdir /user/devuser
# make devuser the owner:
$ sudo -u hdfs hdfs -chown devuser /user/devuser You first elevate to hdfs, then run the hdfs dfs command. This wil create your personal directory in /user and make you the owner. Now, when you run hdfs commands as devuser, you will have permission to modify objects in that folder. CAREFUL: elevating to hdfs is like becoming root in linux. You can do a lot of damage if you make a mistake.
... View more
03-07-2016
07:54 AM
Quick follow-up: I have confirmed that the combination of updating /etc/cloudera-scm-agent/config.ini AND adding --lib_dir= to /etc/defaults/cloudera-scm-agent successfully corrects the startup problem when relocating /var/lib/cloudera-scm-agent. Here is what I did: 1. Stop agent: sudo service cloudera-scm-agent stop 2. Update /etc/cloudera-scm-agent/config.ini: # Particularly, the agent's UUID is stored here. # lib_dir=/var/lib/cloudera-scm-agent lib_dir=/NEW_DIR_PATH 3. Update /etc/default/cloudera-scm-agent: # Specify any command line arguments for the Cloudera SCM Agent here. # CMF_AGENT_ARGS="--lib_dir=/NEW_DIR_PATH " 4. Copy old content of /var/lib/coudera-scm-agent to new location /NEW_DIR_PATH: sudo cp /var/lib/cloudera-scm-agent/* /NEW_DIR_PATH 5. Rename old content (in case we mess up): sudo mv /var/lib/cloudera-scm-agent /var/lib/cloudera-scm-agent-del 6. Restart agent: sudo /sbin/service cloudera-scm-agent start 7. If you are happy and you know it, delete the old lib: sudo rm-rf /var/lib/cloudera-scm-agent-del I am happy. And I appreciate the really quick turn-around!! -Hugh
... View more
03-03-2016
08:02 AM
Hi, Harsh! At least I am not losing my mind 🙂 Ok. I will set this up in my lab and let you know what the outcome is. Thank you for getting back to me on this!! Regards! -Hugh
... View more
02-26-2016
02:38 PM
CM 552 SCM Agent Version: 5.5.3 Centos5.11 We needed to relocate the agent outputs from /var/log and /var/lib because of space restrictions on the root mount. Using config.ini, we were able to sucessfully move log_file to a new location. However, changes to the lib_dir property are wholly ignored and we are fairly sure we are not victims of a phat-phinger attack. Could someone check on this? Thanks! Hugh
... View more
Labels:
- Labels:
-
Cloudera Manager