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

Posted to issues@spark.apache.org by "Igor Berman (JIRA)" <ji...@apache.org> on 2018/04/12 10:26:00 UTC

[jira] [Commented] (SPARK-17519) [MESOS] Enhance robustness when ExternalShuffleService is broken

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

Igor Berman commented on SPARK-17519:
-------------------------------------

Additional usecase: when driver can't connect to one of the external shuffle services it aborts on Mesos, but continues to be alive, so from Mesos perspective framework enters inactive mode(which needs manual restart)

> [MESOS] Enhance robustness when ExternalShuffleService is broken
> ----------------------------------------------------------------
>
>                 Key: SPARK-17519
>                 URL: https://issues.apache.org/jira/browse/SPARK-17519
>             Project: Spark
>          Issue Type: Improvement
>          Components: Mesos
>    Affects Versions: 2.0.0
>            Reporter: Sun Rui
>            Priority: Major
>
> This is intended to be a complement to SPARK-17370 which addressed Standalone mode only.
> For Mesos, it seems we could enhance MesosExternalShuffleClient to detect if any of the external shuffle services is lost when sending heartbeats. In such case, the MesosCoarseGrainedSchedulerBackend can notify ExecutorLost with workerlost=true. Also it can put the slave where the external shuffle service run to the blacklist, preventing launching tasks further on it. 



--
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