Cloudera Manger issues while using VMware : Laptop RAM requirements or something else ?

[#1]

Dear All

I was able to successfully open Quickstart VM and after setting memory as 8 GB it helped start Cloudera Manager (using the Cloudera Express link on Desktop)

But even after setting the VM to use entire 8 GB of the total available RAM and 2 virtual CPU's  , Cloudera Manager starts up but gives following issues :

1. Hosts turns RED with Clock offset issue

2. sometimes , Service monitor doesnt start up 

3. Host Monitor doesnt start up.

Even when I tried restarting the Service Monitor, Host Monitor or  Cluster it starts putting many other components into RED status.

My Laptop's memory is 8GB . Is this happening because the total available memory on the laptop should be greater than 8 GB so that some memory capacity is available for other laptop functions. I was thinking of buying additional 8 GB to expand my laptop RAM to 16 GB based on this logic but wanted to double check whether ths is a known issue due to RAM.

Please let me know if RAM upgrade from 8 GB to 16 GB  will help this or can there be a different cause ?

Regards

[#2 · Accepted solution]

The clock offset issue is likely due to networking configuration, and may
not actually be serious. Cloudera Manager wants to make sure all the
machines' clocks are in sync via NTP. If your VM can't reach the NTP
servers CentOS 6 is configured with be default (often because VMware is set
to a host-only virtual network adapter) it will trigger this warning. If
after restarting the service monitor you're only seeing this warning and
services marked as red because of the host they're running on (I.e. As a
side effect of this warning) you can safely ignore the warning (if you
don't need to dismiss anything from the internet, or tweak VMware's network
setting to allow network access.

[#3 · Accepted solution]

The clock offset issue is likely due to networking configuration, and may
not actually be serious. Cloudera Manager wants to make sure all the
machines' clocks are in sync via NTP. If your VM can't reach the NTP
servers CentOS 6 is configured with be default (often because VMware is set
to a host-only virtual network adapter) it will trigger this warning. If
after restarting the service monitor you're only seeing this warning and
services marked as red because of the host they're running on (I.e. As a
side effect of this warning) you can safely ignore the warning (if you
don't need to dismiss anything from the internet, or tweak VMware's network
setting to allow network access.

[#4]

Thanks Sean.

I did infact ignore the warning but then the next time it started giving error on Service Monitor couldnt start.

All the graphs , and status are not dispalyed when this happens.

Is this also something that can be ignored and we can continue with tutorials. I was keen to use Cloudera Manager too , hence this bottleneck of issues that keep popping up make me feel whether there is something that needs to be corrected before i proceed with any of the tutorials.

Also, do we need overall memory on laptop to be greater than 8 GB if , Cloudera manager required 8 GB to be set on VMware.

Is this something that might be causing the issues with Service monitor etc.

Regards

[#5 · Accepted solution]

Yeah you're likely having issues due to memory constraints. Most of the
tutorial can be completed without Cloudera Manager in 4GB if RAM, if you
want to start with a new instance of the VM. Other than checking the status
of required services before each tutorial in the sequence, the only thing
missing will be using Cloudera Navigator at the end (which will actually
require 10GB+ of memory to launch the Cloudera Enterprise (trial) option)
to audit access to the cluster, data lineage, and security policies.