You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "wuyi (Jira)" <ji...@apache.org> on 2022/12/02 07:56:00 UTC

[jira] [Updated] (SPARK-41360) Avoid BlockManager re-registration if the executor has been lost

     [ https://issues.apache.org/jira/browse/SPARK-41360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

wuyi updated SPARK-41360:
-------------------------
    Summary: Avoid BlockManager re-registration if the executor has been lost  (was: Avoid BlockMananger re-registration if the executor has been lost)

> Avoid BlockManager re-registration if the executor has been lost
> ----------------------------------------------------------------
>
>                 Key: SPARK-41360
>                 URL: https://issues.apache.org/jira/browse/SPARK-41360
>             Project: Spark
>          Issue Type: Improvement
>          Components: Spark Core
>    Affects Versions: 2.4.8, 3.0.3, 3.1.3, 3.2.2, 3.3.1
>            Reporter: wuyi
>            Priority: Major
>
> We should avoid block manager re-registration if the executor has been lost as it's meaningless and harmful, e.g., SPARK-35011



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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