Member since
10-13-2014
119
Posts
9
Kudos Received
13
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
2128 | 04-04-2016 10:25 PM | |
4024 | 02-04-2016 04:13 PM | |
3299 | 02-04-2016 03:59 PM | |
2233 | 11-23-2015 11:11 PM | |
7019 | 10-23-2015 06:36 PM |
11-17-2014
11:24 AM
t2.micro is definitely too small to run all the services. You will immediately get memory exceptions and the JVMs will fail to start for various services (not only Cloudera Manager). t2.micro is also too small to run Director itself. For a small development type of setup I would recommend m1.medium or larger (it depends on how much data you want to process with the cluster). If your goal is to use Hue and experiment with various products have you considered Cloudera Live?
... View more
11-14-2014
11:58 AM
That's great! Any improvement ideas for future release? How could we improve the overall experience of using the product?
... View more
11-12-2014
02:07 PM
Hi Natty! Have you been able to successfully run Director? Any feedback for future releases?
... View more
11-12-2014
01:28 PM
That's great! Can you add a few more details on how you are planning to use Director? It would be useful to make sure future release are aligned with your requirements.
... View more
11-12-2014
01:25 PM
1 Kudo
With regard to "First Run" failure - there should another log message above that explains why that command actually failed and during what step. In the Cloudera Manager UI you should be able to see more details in the command history.
... View more
11-12-2014
01:20 PM
There is something concerning in the output: * Invalid role type(s) specified. Ignored during role creation: HUE: BEESWAX_SERVER ... done Can you please remove BEESWAX_SERVER from the list of roles and retry?
... View more
11-12-2014
01:17 PM
First of all thanks for using Cloudera Director! I am happy to see everything worked fine while configuring multiple medium size clusters. With regard to m2.4xlarge - there is no reason why it shouldn't work when running a supported operating system. I'm re-testing this now. Actually Director should work just fine with any instance type provided by AWS (using either SSDs or magnetic drives for ephemeral storage). In terms of operating systems Director currently works with Red Hat Enterprise Linux 6.4 (PV or HVM)) or CentOS 6.4 (the official AMI from the AWS Marketplace). Amazon Linux (ami-f032acc0) is not currently supported.
... View more
11-11-2014
01:50 PM
For now unfortunately you will to change it back to admin/admin in order to be able to run the update. I will file a feature request on you behalf to make sure we improve this in the next release and document it properly. One last thing. My recommendation would be to use Director 1.0.1 that contains some fixes for issues we've discovered after making the release public. See: http://cloudera.com/content/cloudera/en/products-and-services/director.html for instructions on how to install Director from packages.
... View more
11-11-2014
01:40 PM
Hi David - Have you changed the default Cloudera Manager password from admin/admin to somethind else? That may be the source of this error.
... View more
10-15-2014
09:39 PM
1 Kudo
There may be a mistmatch between the region you want to use and the one that has your key. Most of the resources in AWS are scoped to regions and can't be referenced globally. The ".pem" extension is not needed.
... View more
- « Previous
- Next »