Member since
11-16-2014
41
Posts
4
Kudos Received
1
Solution
My Accepted Solutions
Title | Views | Posted |
---|---|---|
1969 | 11-17-2014 02:34 PM |
04-08-2015
03:40 PM
Sorry, the ticket is in our internal JIRA. We're targeting 1.1.2 and 1.5.0 releases for these fixes. Here's a link to the other message thread discussing the proxy issue http://community.cloudera.com/t5/Cloudera-Director-Cloud-based/cloudera-director-bootstrap-failed-on-quot-hostname-Unknown-host/m-p/26291#U26291.
... View more
11-17-2014
05:11 PM
> What would happen if I tried adding the nodes back in via the manager 'add new hosts to cluster'? The behavior is undefined. Director needs to do that on its own. It can't deal with external cluster topology modifications.
... View more
11-17-2014
02:34 PM
1 Kudo
Fixed by picking a different AMI, the original AMI had multiple partitions on the root disk which the director install did not appreciate. Switching to an AMI with a single partition on the root volume appears to have resolved this issue entirely. FWIW the picking the official centos AMI should ensure you dont have a bad time.
... View more
11-17-2014
11:33 AM
The director actually doesn't perform terribly on a t2.micro and I don't recall getting any exceptions or OOM errors. The manager and cluster nodes were the issue. We're already running a CDH 5 cluster with Spark. I'm interested in using director as a replacement to our current methods of creating/deploying/scaling/managing clusters. Will try creating a more realistic cluster now.
... View more