You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Sean R. Owen (Jira)" <ji...@apache.org> on 2021/09/26 00:58:00 UTC

[jira] [Commented] (SPARK-36584) ExecutorMonitor#onBlockUpdated will receive event from driver

    [ https://issues.apache.org/jira/browse/SPARK-36584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17420171#comment-17420171 ] 

Sean R. Owen commented on SPARK-36584:
--------------------------------------

Maybe, but, if you're saying you don't know if it's a problem and don't have a change to suggest, not sure what to do with this.

> ExecutorMonitor#onBlockUpdated will receive event from driver
> -------------------------------------------------------------
>
>                 Key: SPARK-36584
>                 URL: https://issues.apache.org/jira/browse/SPARK-36584
>             Project: Spark
>          Issue Type: Question
>          Components: Spark Core
>    Affects Versions: 3.1.2
>         Environment: Spark 3.1.2
>            Reporter: 胡振宇
>            Priority: Minor
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
>  When driver broadcast object, it will send the [SparkListenerBlockUpdated|https://github.com/apache/spark/blob/df0ec56723f0b47c3629055fa7a8c63bb4285147/core/src/main/scala/org/apache/spark/scheduler/SparkListener.scala#L228] event. [ExecutorMonitor#onBlockUpdated|https://github.com/apache/spark/blob/df0ec56723f0b47c3629055fa7a8c63bb4285147/core/src/main/scala/org/apache/spark/scheduler/dynalloc/ExecutorMonitor.scala#L380] receives and handles the event, in this method, 
>  it calls [ensureExecutorIsTracked|https://github.com/apache/spark/blob/df0ec56723f0b47c3629055fa7a8c63bb4285147/core/src/main/scala/org/apache/spark/scheduler/dynalloc/ExecutorMonitor.scala#L489]
>  to put driver in `executors` variable with `UNKNOWN_RESOURCE_PROFILE_ID`. In my understanding, `ExecutorMonitor` should only monitor executor not driver.  Although this will not cause any problems at the moment because UNKNOWN_RESOURCE_PROFILE_ID will be filtered out, but I think this is a potential risk



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org