Member since
11-15-2013
17
Posts
2
Kudos Received
0
Solutions
01-09-2020
08:22 PM
you could also resize the mountpoint if you think it is oversized. sudo mount -o size=10G -o remount cm_processes. After I resize from 71GB to 10GB, I don't find any different in "free -h". So I feel the tmpfs doesn't really block the physical memory ahead. Taken from following reference. http://man7.org/linux/man-pages/man5/tmpfs.5.html rgds, Rama.
... View more
11-23-2016
07:37 AM
Unfortunately there is no way to provide super user access to an entire group today. It must be done one user at a time. There is a feature request to add this in a future release. You could do it programatically to make it a little easier, see the section "How to make a certain user a Hue admin" http://gethue.com/password-management-in-hue/ You could create a list of users and iterate through them in hue shell. Make sure to set HUE_CONF_DIR=/var/cloudera-scm-agent/process/id-hue-HUE_SERVER where id is most recent. ON CDH 5.5 and above you also have to set: export HUE_IGNORE_PASSWORD_SCRIPT_ERRORS=1 export HUE_DATABASE_PASSWORD=huedatabasepassword Hope this helps.
... View more
03-18-2016
03:10 PM
1 Kudo
In HDFS, the permissions model for owner and group follow the BSD rule. The owner is set to the authenticated user, but the group is inherited from the parent directory. This is documented in the Permissions Guide: http://archive.cloudera.com/cdh5/cdh/5/hadoop/hadoop-project-dist/hadoop-hdfs/HdfsPermissionsGuide.html#Overview """ When a file or directory is created, its owner is the user identity of the client process, and its group is the group of the parent directory (the BSD rule). """ The Group Mapping is purely used at the authorisation side, not at the creation side as you are expecting it to be. Since your /user/username directory's group is by default the username itself, that's the value you will naturally see for all groups. If you'd like that changed, you will need to chgrp the /user/username directory to be username:user-group instead of username:username. Subsequent files will now be created with username:user-group under it.
... View more
07-25-2014
07:37 AM
1 Kudo
Hi Greg, You found the correct way to do things, so you're already well on the way! Let's get your configuration overrides removed so th global can take precedence. Cloudera Manager will be aware that you have host-level overrides and in fact provides a way to help you batch them back to default such that they inherit this from the global setting. Here are a few screenshots of how that would look: Go to the Hosts tab, then Configuration tab. Click Monitoring on the left side and find the Cloudera Manager Agent Parcel Directory Free Space Monitoring setting you've changed. There should be grey text "Overridden by N host(s)". Expand this, then click Edit Overrides. On the overrides screen you can click the top-most checkbox to select ALL hosts for which you individually applied overrides, and tell them to revert back to inheriting their configuration from the global level: Now return to the Hosts tab, then Configuration tab. Click Monitoring on the left side and find the Cloudera Manager Agent Parcel Directory Free Space Monitoring configuration property. You'll find that in the property coulmn for this, there is no mention of overrides. All hosts are now using this global setting. Congratulations! Repeat for 'Cloudera Manager Agent Parcel Directory Free Space Monitoring Percentage Thresholds' or others as necessary. Hope this helps, -- Mark S.
... View more