You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Dongjoon Hyun (Jira)" <ji...@apache.org> on 2021/08/30 16:11:00 UTC
[jira] [Resolved] (SPARK-36614) Executor loss reason shows "worker
lost" rather "Executor decommission"
[ https://issues.apache.org/jira/browse/SPARK-36614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dongjoon Hyun resolved SPARK-36614.
-----------------------------------
Fix Version/s: 3.1.3
3.2.0
Resolution: Fixed
Issue resolved by pull request 33868
[https://github.com/apache/spark/pull/33868]
> Executor loss reason shows "worker lost" rather "Executor decommission"
> -----------------------------------------------------------------------
>
> Key: SPARK-36614
> URL: https://issues.apache.org/jira/browse/SPARK-36614
> Project: Spark
> Issue Type: Sub-task
> Components: Spark Core
> Affects Versions: 3.1.2, 3.2.0, 3.3.0
> Reporter: wuyi
> Assignee: wuyi
> Priority: Major
> Fix For: 3.2.0, 3.1.3
>
> Attachments: WeChat13c9f1345a096ff83d193e4e9853b165.png
>
>
> For a lost executor caused by decommission, the loss reason shows "worker lost", while it is actually due to decommission.
--
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