[
https://issues.apache.org/jira/browse/SPARK-23346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16369600#comment-16369600
]
Dongjoon Hyun commented on SPARK-23346:
---------------------------------------
Thank you for reporting. I adjusted the priority to `Critical` since it's
reported in 2.2.0. This might be critical, but cannot be a blocker for Apache
Spark 2.3.0.
> Failed tasks reported as success if the failure reason is not ExceptionFailure
> ------------------------------------------------------------------------------
>
> Key: SPARK-23346
> URL: https://issues.apache.org/jira/browse/SPARK-23346
> Project: Spark
> Issue Type: Bug
> Components: Spark Core, SQL
> Affects Versions: 2.2.0
> Environment: HADOOP 2.6 + JDK1.8 + SPARK 2.2.0
> Reporter: 吴志龙
> Priority: Critical
> Attachments: 企业微信截图_15179714603307.png, 企业微信截图_15179715023606.png
>
>
> !企业微信截图_15179715023606.png! !企业微信截图_15179714603307.png! We have many other
> failure reasons, such as TaskResultLost,but the status is success. In the web
> ui, we count non-ExceptionFailure failures as successful tasks, which is
> highly misleading.
> detail message:
> Job aborted due to stage failure: Task 0 in stage 7.0 failed 10 times, most
> recent failure: Lost task 0.9 in stage 7.0 (TID 35, 60.hadoop.com, executor
> 27): TaskResultLost (result lost from block manager)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
