Member since
07-12-2013
435
Posts
117
Kudos Received
82
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 2336 | 11-02-2016 11:02 AM | |
| 3625 | 10-05-2016 01:58 PM | |
| 8288 | 09-07-2016 08:32 AM | |
| 8902 | 09-07-2016 08:27 AM | |
| 2520 | 08-23-2016 08:35 AM |
01-07-2016
11:40 AM
1 Kudo
That command depends on the previous 2: cd /opt/examples/flume solrctl --zk quickstart:2181/solr instancedir --create live_logs ./solr_configs Did you execute those? And if so, were there any error messages?
... View more
01-06-2016
09:12 AM
The message referring to keyboard / mouse capture simply means that moving the focus from your host desktop to the virtual machine will not happen seamlessly. When you click in the VM, it locks your mouse cursor inside it, and you have to press a special key combination to move the mouse cursor back out. Sometimes it's possible to configure the VM so that the mouse can just move freely in and out. It shouldn't affect copy / paste. Can you be very specific about where you're copying and pasting to? It's unclear whether your talking about copying from the web browser, or pasting into the terminal, or what. If you can narrow down exactly what part of that is failing, that would help. Another factor is if you're trying to copy something from your host to the VM and vice-versa. That usually requires special set up to work, and the specific depend on what platform you're using (VMware, VirtualBox, etc.)
... View more
01-06-2016
06:32 AM
The keyboard shortcuts for copy / paste in the terminal are Ctrl + Shift + C and Ctrl + Shift + V (respectively). Have you tried those? They're not supposed to be disabled...
... View more
01-05-2016
08:57 AM
1) I don't know what the issue is with connecting to MySQL. Definitely ensure that MySQL is running (sudo service mysqld status; sudo service mysqld restart). The configuration is in /etc/cloudera-scm-server/db.properties. 2) We do not have a recommended solution for running Hadoop on Docker. Director currently supports cloud platforms like AWS but not Docker. Docker is somewhat counter-productive for production Hadoop clusters because even though Hadoop is designed to get a bunch of machines to work together, having the cluster split into fewer, bigger pieces is better. Docker essentially partiations a machine into smaller pieces. It can be handy for testing, etc. when performance doesn't matter, but it requires a lot of networking setup to make DNS and IP addresses, etc. work the way Cloudera Manager and Hadoop assume they do.
... View more
01-05-2016
08:41 AM
2 Kudos
You're supposed to replace {{cluster_data.manager_node_hostname}} with the hostname of the MySQL server, which on Cloudera Live is the Manager Node. If you're using Cloudera Live, you should refer to the copy of the tutorial as linked to in your welcome email. It will resolve all such variables for your specific cluster. The copy on the website is just for informational purposes - the procedure assumes a lot about the cluster, so you should really just use the copy that's on your cluster.
... View more
01-04-2016
06:34 AM
Your instances need to stay up at least until the deployment is finished. Since IP addresses are likely to change when you restart an instance, it's unpredictable what's going to happen if you stop the machines in the middle of the installation. You'll need to delete your stack and redeploy with a new access code. Details on safely stopping and starting the cluster after it is deployed can be found here under 'Stopping and Starting Instances': http://www.cloudera.com/content/www/en-us/get-started/cloudera-live/aws-documentation.html.
... View more
12-22-2015
08:21 AM
5 Kudos
Kevin, 4096 MB should be sufficient unless you want to launch Cloudera Manager. All of the CDH services should be able to start up and simple examples should work pretty reliably. As for your issue, I would suggest going to File -> Import Appliance... and opening the .ovf file in the directory you unzipped. That file will set up the virtual hardware for you (instead of you setting up everything but the hard disk) so it eliminates a lot of variables. Not sure what the root cause of the issue is, but that's a good first step.
... View more
12-17-2015
10:51 AM
The software is not installed as soon as the stack is created - the deployment of all the sofware is done by a service that you need to register with (to get an access code to uniquely identify your cluster). Creating the stack just provisions the required hardware and those instances then check in with the service and start the deployment process. You'll get an email once that process has started with a link to a progress bar, and an email when it's done and you can safely use the cluster. If you did not already register for an access code, you can sign up for one here: http://www.cloudera.com/content/www/en-us/get-started/cloudera-live.html. If you did get an access code, send me a private message with the code and I can check on the status of your specific cluster and see what's going on.
... View more
12-17-2015
07:38 AM
If you can send me your access code in a private message I can look up what's going on with your cluster.
... View more
12-14-2015
02:30 PM
1 Kudo
Any chance you could take a look at /var/log/hue/hue.log after the container starts up? The boot log doesn't give any information other than the fact that it did fail...
... View more