Hi GaryS,   (1) Can you verify connectivity between Director host and Cloudera Manager host (maybe try pinging Cloudera Manager from Director host). The Director server logs may also contain more information on why the connection validation failed. You can refer here to see how to access the server logs:   https://www.cloudera.com/documentation/director/latest/topics/director_troubleshoot.html   (2) Unfortunatly, nodes can only be added/removed through the UI, it can't be done via config files. Though in your case since Director server can't reach Cloudera Manager, it would fail regardless, since this connectivity is required to properly add nodes to a cluster.   ... View more

Thanks dturner, I'll request to move this to the Cloudera Manager forums. First run, and the scripts associated with it are handled by Cloudera Manager, so they may have more context on whether such hacks are needed. ... View more

Hi dturner,   I just attempted this and wasn't able to reproduce the issue. My cluster creation which included Hue succeeded using CM+CDH 6.2 with CentOS7.6.   In fact I couldn't even find the offending package (wrapt) anywhere on the Hue instance, so there's something different in our environments/installation.   Maybe more information about the enviornment/configuration would help narrow down the problem (whether your using preloaded/prextracted images, AWS or Azure, any special bootstrap scripts, etc) ... View more

@Baris Glad you got it working. With Director version 2.4+ you actually don't need to use a bootstrap script as shown in my previous example. You can just specify the CSD URL on the conf file and Director will automatically download and place it in ' /opt/cloudera/csd/'.   See the documentation here: https://www.cloudera.com/documentation/director/latest/topics/director_non-cdh_products_custom_descriptors.html#concept_e2y_dpj_4z ... View more

Glad you got it working.   Just to note something like this did work for me for hvm instance types:   hvm=c5.large,\ c5.xlarge,\ c5.2xlarge,\ c5d.2xlarge   There should be a ec2.virtualizationmappings.properties.example file you can look at, modify as an example. ... View more

Hmm, so  etc/ec2.virtualizationmappings.properties is the default location to specify the virtualization mapping. You can use etc/ec2.customvirtualizationmappings.properties as shown in your example but then you would have to specify this custom location in etc/aws-plugin.conf (as mentioned in the docs). Can you double check to see if that's the issue. ... View more

These new instance types aren't in Director yet. For now however, you should be able to update Director's AWS plugin to include them. You can refer to the documentation for the steps: https://www.cloudera.com/documentation/director/latest/topics/director_aws_new_instance_types.html ... View more

You can find Cloudera Management Service properties here:   https://www.cloudera.com/documentation/enterprise/properties/5-15-x/topics/cm_props_mgmtservice.html ... View more