Details
-
Improvement
-
Status: Resolved
-
Critical
-
Resolution: Fixed
-
1.5.0
-
None
-
None
Description
We have memory starving problems for a long time, it become worser in 1.5 since we use larger page.
In order to increase the memory usage (reduce unnecessary spilling) also reduce the risk of OOM, we should manage the memory in a cooperative way, it means all the memory consume should be also responsive to release memory (spilling) upon others' requests.
The requests of memory could be different, hard requirement (will crash if not allocated) or soft requirement (worse performance if not allocated). Also the costs of spilling are also different. We could introduce some kind of priority to make them work together better.
Attachments
Issue Links
- is duplicated by
-
SPARK-11348 Replace addOnCompleteCallback with addTaskCompletionListener() in UnsafeExternalSorter
- Resolved
- links to