Details
-
New Feature
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
3.0.0
Description
It would be useful for users to be able to enable dynamic allocation without the need to provision an external shuffle service. One immediate use case is the ability to use dynamic allocation on Kubernetes, which doesn't yet have that service.
This has been suggested before (e.g. https://github.com/apache/spark/pull/24083, which was attached to the k8s-specific SPARK-24432), and can actually be done without affecting the internals of the Spark scheduler (aside from the dynamic allocation code).
Attachments
Issue Links
- is related to
-
SPARK-31645 Improve ExecutorMonitor shuffle-tracking to handle speculative tasks properly
- Open
- relates to
-
SPARK-24432 Add support for dynamic resource allocation
- Open
-
SPARK-28487 K8S pod allocator behaves poorly with dynamic allocation
- Resolved
- links to