Details
-
Sub-task
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
Description
The spark.shuffle.spill=false configuration doesn't make much sense nowadays: I think that this configuration was only added as an escape-hatch to guard against bugs when spilling was first added. Similarly, setting spark.sql.planner.externalSort=false doesn't make sense in newer releases: many new implementations, such as Tungsten, completely ignore this flag, so it's not applied in a consistent way.
In order to reduce complexity, I think that we should remove the ability to disable spilling. Note that the tungsten-shuffle manager already does not respect this setting, so removing this configuration is a blocker to being able to unify the two sort-shuffle implementations.
Attachments
Issue Links
- blocks
-
SPARK-10708 Consolidate SortShuffleManager and UnsafeShuffleManager
- Resolved
- is related to
-
SPARK-50482 Deprecated no-op `spark.shuffle.spill` config
- Resolved
- links to