Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

Cloudera service and host monitoring fails frequently in cloudera-quickstart-vm-5.7.0.

Solved Go to solution
Highlighted

Cloudera service and host monitoring fails frequently in cloudera-quickstart-vm-5.7.0.

Explorer

Hello, I am facing a a lot of issue in running Cloudera Managemment Service and Cloudera Quickstart services.I have given 8GB RAM but still the service and host monitior fails frequently. The services running on my VM are:

1. Flume

2. HDFS

3. Kafka

4. Spark

5. Sqoop 1 Client

6. Sqoop 2

7. YARN (MR2)

8. Zookeeper

For about 5 minutes it's up and the signals are green, then gradually it changes to yellow and then complete red. What to do? How to make it up running every time? I have given enough memory to each and evrey service. Please suggest me. What am I doing wrong. The error messages I get are " Failed to connect the cloudera host", "Failed to start the service and host monitor". Please help me. How can I proceed with my project if these services are not running properly. I am stuck.

1 ACCEPTED SOLUTION

Accepted Solutions

Re: Cloudera service and host monitoring fails frequently in cloudera-quickstart-vm-5.7.0.

Master Collaborator
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 solution in original post

1 REPLY 1

Re: Cloudera service and host monitoring fails frequently in cloudera-quickstart-vm-5.7.0.

Master Collaborator
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 solution in original post

Don't have an account?
Coming from Hortonworks? Activate your account here