dturner,   We don't have any documented recommendations for the max deployments or clusters. Anecdotally, I've heard of 100+ clusters. Director does the most work when bootstrapping/updating/terminating clusters and less when just monitoring clusters.    You are also running on a way larger instance than we usually use so I bet there's room for some tuning if you do run into issues (e.g., increasing memory, threadpools, etc). ... View more

iasindev,   The symptoms you describe are due to a bug in the 2.8.0 standalone client. The standalone client commands are deprecated in 2.8.0 and unfortunately suffer from this bug.   In preference order, workarounds are: 1. Use the bootstrap-remote command with a Cloudera Director server. This is the preferred configuration. or 2. Unset the segment analytics writeKey property for the cli by adding segment.analytics.writeKey: to /etc/cloudera-director-client/application.properties or 3. Use the 2.7.1 standalone client. It does not suffer from this bug.   Good luck! David ... View more

sg321,   I've followed the instructions you linked through cluster bootstrap and successfully created a cluster using ami-2051294a in us-east-1.   I did have to make 1 modification to get the spark2 csd to match the spark2 parcel repo. You can do this by either bumping the csd up to http://archive.cloudera.com/spark2/csd/SPARK2_ON_YARN-2.2.0.cloudera2.jar or pinning the parcel repo to http://archive.cloudera.com/spark2/parcels/2.2.0.cloudera2/   Is this reliably/repeatably failing first run for you? ... View more

Tomas79,   Please refer to the CM and CDH documentation. Use the "API Name" https://www.cloudera.com/documentation/enterprise/properties/5-15-x/topics/cm_props_cdh5150.html   Note that "Service-wide" configurations are specified at the cluster level in the serviceConfigs block while the role-specific configurations are specified per instance group in the roleTypeConfigs blocks.   David ... View more

dturner,   The clusters will be independent.   There is one minor caveat. Director finds the instances in AWS based on their "Cloudera-Director-Id" tag. Cloudera Director uses UUIDs for these so they will be unique across all instances. However, Cloudera Director accepts any String for this ID if you are creating your cluster through the API (i.e., not through Cloudera Director's UI or CLI). In that case, it is incumbent upon you to ensure you don't have any ID conflicts.   Here's an example of how you could get into trouble. If you GET a ClusterTemplate through the API, change the "name", and POST it back to create a new Cluster. Director may find the wrong instances in AWS. To avoid this, you must also change all the "id" fields for all of the "virtualInstances".   ... View more