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.

What is the best practice to ensure consistency of YARN jobs in event of disaster.

Highlighted

What is the best practice to ensure consistency of YARN jobs in event of disaster.

Super Guru

If a YARN job fails due to a cluster crashing. How do we know the status? What is the best way to prepare for this?

What best practices around DR should we do to maintain integrity of Oozie, Spark, Hive, HBase jobs.

We want to know if jobs completed successfully / failed, and any other information available.

Were writes consistent, etc..

Data lost? Can / should each job be rerun.

Consistency

Availability

We don't want to lose data, corrupt data or rerun jobs that don't need to be run. Rerunning some jobs may be an issue as not all are idempotent.

Data ingest jobs can't be rerun.

Some analytics jobs can be.

Anything cloud specific would be helpful as well.

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