Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
1.0.0
-
None
-
None
Description
In yarn environment, let's say :
MaxAM = Maximum allocatable memory
ExecMem - Executor's memory
if (MaxAM > ExecMem && ( MaxAM - ExecMem) > 384m ))
then Maximum resource validation fails w.r.t executor memory , and application master gets launched, but when resource is allocated and again validated, they are returned and application appears to be hanged.
Typical use case is to ask for executor memory = maximum allowed memory as per yarn config
Attachments
Issue Links
- relates to
-
SPARK-2140 yarn stable client doesn't properly handle MEMORY_OVERHEAD for AM
- Resolved
- links to