When scheduling Structured Streaming jobs for production, which configuration automatically recovers from query failures and keeps costs low?

Question

Options

• ACluster: New Job Cluster;
• BCluster: New Job Cluster;
• CCluster: Existing All-Purpose Cluster;
• DCluster: Existing All-Purpose Cluster;
• ECluster: Existing All-Purpose Cluster;

• A
  12% (3)
• C
  8% (2)
• D
  77% (20)
• E
  4% (1)

Explanation

The configuration that automatically recovers from query failures and keeps costs low is to use a new job cluster, set retries to unlimited, and set maximum concurrent runs to 1. This configuration has the following advantages: A new job cluster is a cluster that is created and terminated for each job run. This means that the cluster resources are only used when the job is running, and no idle costs are incurred. This also ensures that the cluster is always in a clean state and has the latest configuration and libraries for Setting retries to unlimited means that the job will automatically restart the query in case of any failure, such as network issues, node failures, or transient errors. This improves the reliability and availability of the streaming job, and avoids data loss or inconsistency. Setting maximum concurrent runs to 1 means that only one instance of the job can run at a time. This prevents multiple queries from competing for the same resources or writing to the same output location, which can cause performance degradation or data corruption. Therefore, this configuration is the best practice for scheduling Structured Streaming jobs for production, as it ensures that the job is resilient, efficient, and consistent.

No community discussion yet for this question.