In that case, you can use HDFS ACL and grant mapred user read permissions to all existing and any future file under this directory, to mapred user. https://www.cloudera.com/documentation/enterprise/5-14-x/topics/cdh_sg_hdfs_ext_acls.html#concept_hdfs_extended_ACL_example ... View more

If ownership of "/user/history" has not been set to "hdfs:supergroup" in purpose, then this is simply a configuration issue. This directory should be owned by mapred user. Normally, this directory is automatically created and configured by Cloudera Manager, If you are doing manual installation, then you can check in https://www.cloudera.com/documentation/enterprise/5-9-x/topics/cdh_ig_yarn_cluster_deploy.html#topic_11_4_9 ... View more

I think, what you need first is this https://www.cloudera.com/documentation/enterprise/5-10-x/topics/cm_mc_decomm_host.html If decommission is done successfully (all blocks are available across the remaining Datanodes according to the replication factor) then you can delete the nodes. ... View more

I think what you need is the following   hbase_config= { 'hbase_service_config_safety_valve': '<property><name>regionserver.global.memstore.upperLimit</name><value>0.15</value></property>' } hbase.update_config(hbase_config) I have tested it and it works. There is no need to set "m" with get_config and then re-apply the whole configuration back. You only have to update the specific safety_valve and not all hbase config.   The only catch is that you have to apply all hbase_service_config_safety_valve parameters. The same will happen with your approach because you are not updating only the "regionserver.global.memstore.upperLimit" but you are applying a value to safety valve. Of course you can write additional code, to parse the existing config of safety valve (the xml part) and add or update the regionserver.global.memstore.upperLimit but again change it to json format as per my example. ... View more

I suppose that you have followed Cloudera's instructions and created the temp user with the command below: mysql> grant all on *.* to 'temp'@'%' identified by 'temp' with grant option; Which is fine. In that case you should use the actual hostname instead of localhost. In mysql "%" does not always include "localhost". ... View more

Can you try mysql -h localhost -u temp -p just to verify that mysql server accepts connections?   Also, can you check if SELinux is enabled? getenforce If the output is "1" then you should disable it. Temp change setenforce 0 ... View more

You need the truststore. Check this link https://www.cloudera.com/documentation/enterprise/5-11-x/topics/sg_add_root_ca_explicit_trust.html#id_for_this_topic where it is documented. ... View more

My mistake. Cloudera works with json not xml. Anyhow, to upload complete cluster config you can do it by following https://gist.github.com/gwenshap/7044525 but this is for serious cases. On the other hand, you can push only HBase configuration with the previous links I send you. You just have to prepare config in json format. ... View more

From command line I don't know if there is a way to upload xml for a specific service. You can do it for the cluster. But you should check https://cloudera.github.io/cm_api/apidocs/v19/path__clusters_-clusterName-_services_-serviceName-_config.html and https://cloudera.github.io/cm_api/apidocs/v19/path__clusters_-clusterName-_services_-serviceName-_roles_-roleName-_config.html You can also modify parameters by using PUT instead of GET ... View more