Member since
10-13-2014
119
Posts
9
Kudos Received
13
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
2206 | 04-04-2016 10:25 PM | |
4121 | 02-04-2016 04:13 PM | |
3473 | 02-04-2016 03:59 PM | |
2335 | 11-23-2015 11:11 PM | |
7407 | 10-23-2015 06:36 PM |
04-08-2015
11:20 AM
Reverting to 1.0.2 may work. That authorization exception should not happen if you can successfuly login. Can you give it another try in incognito mode? (just to make sure there are no other cookies in your browser)
... View more
04-08-2015
10:49 AM
Unfortunately this is a known upgrade bug that we will be fixing in the 1.1.2 patch release that will be available soon. The issue has to do with the fact that the list of parcel repositories is empty on the cluster created via 1.0.x. You should be able to grow a cluster created with 1.1.1 in the first place as expected. Is it possible for you to migrate the data from the existing cluster?
... View more
03-27-2015
10:27 AM
Was this cluster configured using Cloudera Director on AWS? Can you provide more details on how you do DNS and hostname configuration?
... View more
12-09-2014
03:27 PM
Great! I've also missed that in your initial post. This sounds like something we can warn about during configuration file parsing. I will file an internal feature request to improve it. Do placement groups improve things from a network latency perspective for you as expected?
... View more
12-08-2014
06:01 PM
1 Kudo
Thanks for reporting! We are still testing this out and we will reply with more details soon. When using Placement Groups you should know about the following limitations: http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/placement-groups.html
... View more
12-04-2014
05:09 PM
Forgot to mention. You also need to install Oracle JDK by doing: sudo apt-get install oracle-j2sdk1.7
... View more
12-04-2014
03:22 PM
Sorry for making this hard. We are the in the process of improving the download page. For 12..04 LTS (precise) here are the commands you should run (assuming wget is installed). You should run them from a machine running in AWS. $ wget http://archive.cloudera.com/director/ubuntu/precise/amd64/director/cloudera-director.list $ wget http://archive.cloudera.com/director/ubuntu/precise/amd64/director/archive.key $ sudo apt-key add archive.key $ sudo mv cloudera-director.list /etc/apt/sources.list.d $ sudo apt-get update $ sudo apt-get install cloudera-director-client cloudera-director-server $ sudo service cloudera-director-server start At the end of this Director should be available on port 7189 on that machine. You should be able to access it from a browser via a tunnel, proxy or VPN connection. For more instructions see the documentation: http://cloudera.com/content/cloudera/en/documentation/cloudera-director/latest/PDF/cloudera-director.pdf
... View more
12-04-2014
03:02 PM
You can customise the configuration file to add Spark. AWS Quickstart does not automatically create the cluster. See docs.
... View more
12-04-2014
02:25 PM
In this case my recommendation would be to try out AWS Quickstart. It makes it very easy to setup everyhing (handles installation automatically). Here are the relevant links that explain all the moving parts: http://blogs.aws.amazon.com/bigdata/post/Tx2D0J7QOVRJBRX/Deploying-Cloudera-s-Enterprise-Data-Hub-on-AWS http://aws.amazon.com/about-aws/whats-new/2014/10/15/clouderas-enterprise-data-hub-edh-on-aws-quick-start/ http://aws.amazon.com/blogs/aws/aws-quickstart-cloudera/ http://aws.amazon.com/quickstart/ Are you already using AWS for other applications? Can you provide more details on your use case?
... View more
12-04-2014
02:15 PM
As a reminder: make sure you are running Director on a machine withing the desired subnet in VPC. When configuring clusters it tries to access nodes on the private network.
... View more