Member since
08-08-2013
31
Posts
7
Kudos Received
7
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
2798 | 03-20-2017 04:52 PM | |
3495 | 10-04-2016 01:51 PM | |
4719 | 07-12-2016 06:41 PM | |
7579 | 06-16-2016 05:35 PM | |
2391 | 01-30-2016 04:10 PM |
08-01-2017
06:15 PM
Do you use cloud infrastructure for your CDH clusters? You are invited to share your feedback on your usage and management of cloud infrastructure. You will thereby influence the roadmap of Cloudera Director and other cloud orchestration software from Cloudera. Please share your experiences by taking this short survey: http://tiny.cloudera.com/director-survey Key Cloudera Director features recently added include: Automatic repair of clusters Support for long-running clusters: Cloudera Director now syncs with cluster changes made via Cloudera Manager AWS Spot instance support and improved resiliency to spot instance disappearances Support for AWS EBS volumes Support for Azure ADLS, Azure premium and standard storage For more details on which versions support different features, please refer to the release notes. If you have any questions or comments, you can reach me at vinithra@cloudera.com. Thanks for your input, Vinithra Varadharajan Engineering Manager, Cloud
... View more
07-24-2017
08:23 AM
Can you give me the exact AMI IDs that you are using to try out?
... View more
04-13-2017
09:09 AM
Yoga, I just tried to repro your problem and I see a BYON-specific instance template popup. One thing to note that may be confusing you is that Director requires an Type and Image field even though these concepts are not needed in BYON. Feel free to put anything you want in those fields. If you click on the "Advanced Options", you can specify the preferred hosts for that template. Director will attempt to pick a host from that list on a best effort basis. David
... View more
03-21-2017
01:13 AM
Thanks! I will put this in the cluster config and try: ... YARN { yarn_service_config_safety_valve: """ <property> <name>yarn.nodemanager.log-aggregation.roll-monitoring-interval-seconds</name> <value>3600</value> </property> """ } ...
... View more
10-04-2016
01:58 PM
1 Kudo
Does this list of configuration properties help: http://www.cloudera.com/documentation/enterprise/properties/5-7-x/topics/cm_props.html
... View more
09-19-2016
05:41 AM
Vinithra, Thanks, thats pretty much what I thought, but wanted to make sure! Berg
... View more
07-13-2016
10:51 AM
Kudu will be supported in Cloudera Director when Kudu goes GA. Can you give us more details on how you are using Director and your experience so far?
... View more
01-31-2016
01:37 PM
Thankyou for the quick update Vinithra, much appreciated. Regards, Damion.
... View more
10-14-2015
02:07 PM
For your reference, here are the contents of reference.conf inside the jar: # # Copyright (c) 2013 Cloudera, Inc. All rights reserved. # deploymentName: ${?name}" Deployment" environmentName: ${?name}" Environment" # # Generic defaults that apply to all configuration files # cloudera-manager { username: admin password: admin } cluster { products { CDH: 5 # latest from 5.x branch } } roles { HDFS_MASTERS: [NAMENODE, SECONDARYNAMENODE] HDFS_WORKERS: [DATANODE] MAPREDUCE_MASTERS: [JOBTRACKER] MAPREDUCE_WORKERS: [TASKTRACKER] YARN_MASTERS: [RESOURCEMANAGER, JOBHISTORY] YARN_WORKERS: [NODEMANAGER] ZOOKEEPER_MASTERS: [SERVER] ZOOKEEPER_WORKERS: [] HBASE_MASTERS: [MASTER] HBASE_WORKERS:[REGIONSERVER] HIVE_MASTERS: [HIVESERVER2, HIVEMETASTORE] HIVE_WORKERS: [] OOZIE_MASTERS: [OOZIE_SERVER] OOZIE_WORKERS: [] HUE_MASTERS: [HUE_SERVER] HUE_WORKERS: [] IMPALA_MASTERS: [CATALOGSERVER, STATESTORE] IMPALA_WORKERS: [IMPALAD] SQOOP_MASTERS: [SQOOP_SERVER] SQOOP_WORKERS: [] FLUME_MASTERS: [] FLUME_WORKERS: [AGENT] SOLR_MASTERS: [SOLR_SERVER] SOLR_WORKERS: [] SPARK_ON_YARN_MASTERS: [SPARK_YARN_HISTORY_SERVER] SPARK_ON_YARN_WORKERS: [] SENTRY_MASTERS: [SENTRY_SERVER] SENTRY_WORKERS: [] }
... View more
07-15-2015
07:18 PM
Hi Kirk - > 1. The application log doesn't reveal the aws CLI commands that are run. Is there a way to > see those commands? Either before (as a dry run feature) or after? Cloudera Director integrates with the AWS API using the Java SDK. There is no straightforward way to translate those method calls as AWS CLI commands you can run standalone. In theory you should be able to figure out how to use the AWS CLI to start similar instances by inspecting the existing ones. > 2. The nodes that get provisioned do not have anything in the /etc/hosts file. How are they resolving each other? > Typically, the hosts file configuration is critical to getting Cloudera Manager to run successfully. We expect DNS configuration to be handled outside of Cloudera Director using different mechanisms: VPC configuration to use AmazonProvidedDNS via DHCP Options Sets custom bootstrap script that Director runs to configure the hostname scripts embedded into a custom AMI that configure the proper hostname during boot and handle DNS registration Cloudera Director doesn't attempt to perform any DNS configs.
... View more