Thanks for a quick response.    I already had this setting set to "Active Directory" since I exported and then imported the cloudera manager configuration.   However when I tried again today I was able to generate missing credentials and the error I got last time was gone.   The two things I did differently from the previous time I've tried that could have influenced something are the following:   1. Did reinstall of "yum reinstall openldap-clients -y" on all nodes. 2. Stopped the cloudera-scm-server on the host that was running the CM services before (last time this service was running both on the new and the old CM hosts).    Note: When I brough up the new Cloudera Manager it showed all sevices as stopped even though I left them running in the old CM. Then when I tried to start them they failed with "address in use" and similar. I had to repoint all nodes to the old CM again, then shutdown the cluster from the old CM and then point all nodes to the new CM. Then the services started fine with the execption of the Sentry service for which I had to reboot the host its was running on to make it release the pids and lock files it was holding.  ... View more

As suspected there were no available datanodes to place replicas to as I had default replication factor of 3 and 3 datanodes in total.    The balancer started working fine after adding a fourth datanode to the cluster. ... View more

So we shutdown the cluster in order to upgrade the network cards to 10Gbit on all machines. It worked flawlessly after the cluster came back up again. The same transformation is now taking around 5 mins every time and the load on the cluster is mild.   Not sure if the mismatch in network speeds between the nodes or some sort of a lumbo state that the cluster was in was the problem. Maybe it was even a combination of those two. Now it works as expected. Thanks for the help @mbigelow ... View more

Thanks @lhebert for taking the time to answer.    I manages to fix it in the following way: during my initial setup I assigned roles to the different nodes, which then led to the error that I mentioned.Then I uninstalled my setup and created a POC cluster with the one click installer in order to see if this will work, which it did. So I uninstalled the POC cluster and setup my initial cluster again, this time I changed assignment of just a few of the roles and left the rest of the services running on the same node (which was the default assignment). Then the cluster was able to load properly after which I manually moved service roles around in the way I wanted them.   So it seems that the custom role assignment I did broke something.    ... View more

Hi... this is old, but just came across it.   hiveserver2_enable_impersonation is set at the HiveServer2 role level, so you would need to use the full path to your HiveServer2 role.  for instance:   curl -X PUT -H "Content-Type:application/json" -u admin:admin -k "https://localhost:7183/api/v12/clusters/cluster/services/hive/roles/hive-HIVESERVER2-609b6bea2fc852513192152e64d3ec19/config" -d '{ "items" : [ { "name" : "hiveserver2_enable_impersonation", "value" : "false" } ] }'   Since the attribute does not exist at the service level (where you attempted to set it), the attribute is not found.   I hope that might help you or others.   Cheers,   Ben ... View more

I was using C5.7.0, thinking it was the latest. Upgrade to C5.7.2 fixes the problem.  ... View more