There's a file at /var/lib/cloudera-quickstart/tutorial/js/config.js you can edit to manually override the detection. Currently it likely contains the line: var managed = true; I'd recommend changing it to: var managed = 'express'; And that should unlock the other parts of the tutorial. Do not that the only parts 'express' unlocks include some sections on checking the health of services required for each step. The 'enterprise' option of CM will also add a section on using Navigator to audit access to the data and trace lineage of data sets. ... View more

The easiest way would be to download and install the JDK version you want from Oracle's website. They offer RPM packages which should work in the VM, or a tarball that you can extract yourself anywhere you like. Once it's installed, make a note of the directory it installed to: the RPMs will install under /usr/lib/jvm or /usr/java or something like that. The directory will include the version in the name, and should have a /bin/ directory underneath it. With that directory, you'll want to update the value of JAVA_HOME in /etc/profile and restart any shell sessions you have open. If you want CDH to use that JDK as well, export JAVA_HOME in /etc/default/bigtop-utils. ... View more

SSH in the VM will listen on port 22 by default. You're hitting port 2222 on your host machine. If you're using VirtualBox, you can set up port forwarding in VirtualBox so that port 2222 on your host machine is forwarded to 22 (this is probably the easiest solution, but that isn't done out of the box). The alternative is to configure the VM to use something other than NAT for the virtual network. If you configure it to bridged networking or a similar option, it will get it's own IP address that you can use to connect to port 22 from your host machine. ... View more

Depending on what you're doing, the Cloudera Management Services are likely not needed for your project. They deal with monitoring the various services. They make it harder to tell from the Cloudera Manager home page if the service is healthy, but if they crash after 5 minutes it shouldn't affect any of the services themselves. In my experience with the VM, often 1 service will fail that impacts the others (often it's the Host Monitor). I'd look at the monitoring data for the services to see which one is going down first, and then dig deeper in it's logs to see what the problem is. 8 GB should not be seen as plenty, but as the absolute bare minimum required. If you're running all of the Cloudera Manager services and putting load on Flume, Kafka and Spark / YARN, I'd expect your VM to be straining to keep up. These are all services designed to run on fairly large clusters, not minimal VMs - it will struggle with certain projects. I'd recommend adding more memory if you're able to - that is likely the reason on of the Cloudera Management Services isn't keeping up. ... View more