Support Questions
Find answers, ask questions, and share your expertise
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Cloudera Community
- Support
- Support Questions
- Who agreed with this topic
Who agreed with this topic
Service and Host monitor failed in CM 5 and cloudera-quickstart-vm-5.7.0.
Labels:
Explorer
Created on 08-10-2016 11:22 PM - edited 09-16-2022 03:34 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello, I am confused for why my CM is showing error and no results of any charts. It was working fine till yesterday and today morning it stopped unexpectedly. The error I am getting is:
Request to the Service Monitor failed. This may cause slow page responses. View the status of the Service Monitor.
Request to the Host Monitor failed. This may cause slow page responses. View the status of the Host Monitor.
I have assigned 8GB of RAM and 2 processors to my VM.
My Cloudera configuration shows:
- Cloudera QuickStart
- ZooKeeper: Service zookeeper has 1 Server. Cloudera suggests at least 3 Servers for ZooKeeper.
- HDFS: Service hdfs has 1 DataNode. Cloudera suggests at least 3 DataNodes for HDFS.
- HDFS: Java Heap Size of NameNode in BytesJava Heap Size of NameNode in Bytes is recommended to be at least 1GB for every million HDFS blocks. Suggested minimum value: 4294967296
- Kafka: Java Heap Size of Broker50 is less than the recommended minimum of 256.
- quickstart.cloudera: Memory Overcommit Validation ThresholdMemory on host quickstart.cloudera is overcommitted. The total memory allocation is 13.7 GiB bytes but there are only 3.7 GiB bytes of RAM (766.5 MiB bytes of which are reserved for the system). Visit the Resources tab on the Host page for allocation details. Reconfigure the roles on the host to lower the overall memory allocation. Note: Java maximum heap sizes are multiplied by 1.3 to approximate JVM overhead.
- quickstart.cloudera: Package installs detected on host with parcelsParcels are in use, but packages were also detected. Cloudera Manager recommends removing the packages. Components affected: crunch,flume-ng,hadoop,hadoop-0.20-mapreduce,hadoop-hdfs,hadoop-httpfs,hadoop-kms,hadoop-mapreduce,hadoop-yarn,hbase,hbase-solr,hive,hive-hcatalog,hue,hue-common,impala,llama,oozie,parquet,pig,sentry,solr,spark,sqoop,sqoop2,zookeeper.
- ZooKeeper: Service zookeeper has 1 Server. Cloudera suggests at least 3 Servers for ZooKeeper.
- Other
- Cloudera Management Service: Java Heap Size of Service Monitor in BytesThe recommended heap size is 1.0 GiB bytes, 768.0 MiB more than is configured.
- Cloudera Management Service: Maximum Non-Java Memory of Service MonitorThe recommended non-Java memory size is 1.5 GiB, 768.0 MiB more than is configured.
- Cloudera Management Service: Java Heap Size of Host Monitor in BytesThe recommended heap size is 1.0 GiB bytes, 768.0 MiB more than is configured.
- Cloudera Management Service: Maximum Non-Java Memory of Host MonitorThe recommended non-Java memory size is 1.5 GiB, 768.0 MiB more than is configured.I am new to Cloudera, so what should I change so that my VM will start working. Please help me. thanks for help in advance.
- Cloudera Management Service: Java Heap Size of Service Monitor in Bytes
