pyspark conf and yarn top memory discrepancies

Viewed 13

An EMR cluster reads (from main node, after running yarn top):

ARN top - 13:27:57, up 0d, 1:34, 1 active users, queue(s): root NodeManager(s): 6 total, 6 active, 0 unhealthy, 2 decommissioned, 0 lost, 0 rebooted Queue(s) Applications: 3 running, 8 submitted, 0 pending, 5 completed, 0 killed, 0 failed Queue(s) Mem(GB): 18 available, 189 allocated, 1555 pending, 0 reserved Queue(s) VCores: 44 available, 20 allocated, 132 pending, 0 reserved Queue(s) Containers: 20 allocated, 132 pending, 0 reserved

                  APPLICATIONID USER             TYPE      QUEUE PRIOR   #CONT  #RCONT  VCORES RVCORES     MEM    RMEM  VCORESECS    MEMSECS %PROGR       TIME NAME
 application_1663674823778_0002 hadoop          spark    default     0      10       0      10       0     99G      0G      18754     187254  10.00   00:00:33 PyS
 application_1663674823778_0003 hadoop          spark    default     0       9       0       9       0     88G      0G       9446      84580  10.00   00:00:32 PyS
 application_1663674823778_0008 hadoop          spark    default     0       1       0       1       0      0G      0G        382        334  10.00   00:00:06 PyS

Note that the PySpark apps for application_1663674823778_0002 and application_1663674823778_0003 were provisioned via the main node command line with just executing pyspark (with no explicit config editing).

However, the application_1663674823778_0008 was provisioned via the following command: pyspark --conf spark.executor.memory=11g --conf spark.driver.memory=12g. Despite this (test) PySpark config customization, that app in yarn fails to show anything other than 0 for the memory (regular or reserved) value.

Why is this?

0 Answers
Related