I am using cloudera director 2.6 in AWS to build a CM/CDH 5.13 cluster.  When using the default Amazon DNS the cluster builds and executes properly - although I have no resolution back to my on-prem services.    Our desire is to have the AWS instances on our corporate DNS so we built a linux AMI that is setup to resolve to our on-prem DNS, and I am using this as the AMI for our cluster instances.  I have changed the settings in AWS to have DHCP options set to point to the same on-prem DNS - additionally I set the 'DNS Resolution' setting to NO.  The ec2 instances created have a name ip_X_X_X_X@ourcompany.com as expected, however there is no resolution for these names.   As a result of theses setting - when i use cloudera director to create a cluster it fails as it is trying to install the agent on the CM Server instance (failure to resolve the hostname).  It appears that we need an automated way to add these new ec2 instances into our on-prem DNS, or is there another solution we are overlooking?    Has anyone else been successful in using a similar configuration?  Do you use a tool to aumoate the entry of instances into the on-prem DNS?      Thanks for any insights you can provide! ... View more

While doing a BDR restore (of hive metadata and data) from s3 into my new cluster, during the Import Hive Metastore step I caught a glimpse of the below message.  This message is not permanent as it quickly moves to display the overall 'command succeeded' message that remains on the screen.  Can anyone help me understand what the 'fetching results failed' message means and if it is something I should be concerned with?  The data comes into the cluster and all appears to be fine.  I am using CDH 5.13 and I have external hive tables with HDFS source and some with S3 source. My cluster is running on AWS ec2 instances.  Thanks for any added insights!   ... View more