Query Timeout
Query Timeout protects cluster resources by stopping queries after they are submitted if they run longer than the configured time limit.
How It Works
- When a query or job is submitted, Yeedu starts tracking its execution time.
- If the query exceeds the configured timeout, it is automatically terminated.
- Timeout rules are applied during job execution, not before submission.
Why It Matters
- Prevents runaway queries
- Ensures fair resource usage across submitted jobs
- Keeps the cluster responsive in multi-user environments
Typical Configuration
- Default timeout (configurable via Spark Config)
- Optional override at session or job level
This ensures that long-running submitted queries do not block cluster resources.