[jira] [Commented] (SPARK-25376) Scenarios we should handle but missed in 2.4 for barrier execution mode

["Imran Rashid (JIRA)" <ji...@apache.org>]

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

Imran Rashid commented on SPARK-25376:
--------------------------------------

I raised some of my concerns on one of the earlier PRs, Xingbo filed follow up issues for a few of them: SPARK-24954, SPARK-24941, https://github.com/apache/spark/pull/21758#discussion_r206682882

I think there may be some more things that concerned me, but I need to review the changes and refresh my memory a bit ...

> Scenarios we should handle but missed in 2.4 for barrier execution mode
> -----------------------------------------------------------------------
>
>                 Key: SPARK-25376
>                 URL: https://issues.apache.org/jira/browse/SPARK-25376
>             Project: Spark
>          Issue Type: Story
>          Components: Spark Core
>    Affects Versions: 2.4.0
>            Reporter: Xiangrui Meng
>            Priority: Major
>
> [~irashid] You mentioned that there are couple scenarios we should handle in barrier execution mode but we didn't in 2.4. Could you elaborate here?
> One scenario we are aware of is that speculation is not supported by barrier mode. Hence a barrier mode might hang in case of hardware issues on one node. I don't have a good proposal here except letting users set a timeout for the barrier stage. Would like to hear your thoughts.
> You also mentioned multi-tenancy issues. Could you say more?
> cc: [~jiangxb1987]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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