OOPS!   Misread and thought you were using CDH 5.4.8!   The same basic documentation applies for CM/CDH 5.8:   Spark Matrix: http://www.cloudera.com/documentation/enterprise/release-notes/topics/rn_consolidated_pcm.html#concept_yzh_1k4_hw Adding a Service via Cloudera Manager: http://www.cloudera.com/documentation/enterprise/latest/topics/cm_mc_add_service.html   Regards,   Ben ... View more

Hi,   The behavior you describe usually indicates that Navigator is exiting and then Cloudera Manager is starting it again. Very commonly, the exit is due to a java.lang.OutOfMemoryError exception.  You can verify this by (in Cloudera Manager) :   - going to Cloudera Management Service --> Instances --> Navigator Metadata Server --> Processes - and then clicking on "stdout" in the bottom middle of the page.   If you see lots of the OOMEs, then Navigator likely needs more heap to perform its operations. If you have enough RAM, you can double the size or start with maybe just 2GB more.   To edit the configuration, go to:   Cloudera Management Service --> Configuration Then, search for "Java Heap Size of Navigator Metadata Server in Bytes"   If you don't see the heap issues in stdout, please let us know.   Regards,   Ben ... View more

Hi,   The "Failed request to SCM: 302" message occurs when the Host Monitor attempts to communicate to Cloudera Manager but the session has expired.  The Host Monitor acts as a client that authenticates to SCM, so it is subject to session restrictions. The error can be ignored as the Host Monitor will re-authenticate and we do see that in your case that occurs.   In fact, a code change to make the message an INFO message rather than ERROR is slated for Cloudera Manager 5.7.2 and 5.8.2.  ... View more