About sat_046

sat_046 · ‎02-01-2023

We are running a spark streaming job which reads data from kafka and writes to RDBMS. We dont want this job to fail easily due to minor fluctuations in cluster health/issue. Write now spark job has configuration to retry 5 attempts before the whole job fails. But all these retries are happening in quick succession , one after another. Is there a way we can put some delay/sleep time between retry attempts for this job?

sat_046 · ‎10-06-2021

I have a new Cloudera Cluster With services being used - Hdfs, Spark, Yarn, Hive, Kafka, Sentry , Oozie, Zookeeper, Streams Replication Manager, Streams Messaging Manager. I am working on implementing some processes in place about how to plan for OS Pathing for cluster nodes , When Services restart would be required and Sequence of steps and all. is there a defined documentation from cloudera in this regard which i can refer to. Any hints please.

sat_046 · ‎10-06-2021

In Cloudera Manager., I could always see this Alert in health Tests Section - NameNode summary: xyz.abc.net (Availability: Unknown, Health: Good), pqr.abc.net (Availability: Unknown, Health: Good). This health test is bad because the Service Monitor did not find an active NameNode. I do not see any service Disruption and both the servers are up and running. Looking for help what need to be checked and why this heath test alert is persistent.

Online	Offline
Last Visited	‎02-10-2023 01:36 AM

Date Registered	‎10-06-2021 09:44 PM
Last Visited	‎02-10-2023 01:36 AM
Total Messages Posted	4

How to introduce delay time between retry attempts...

Services Restart Strategy for Cloudera Hadoop Clus...

Name Node Health Bad