You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Jiang Xingbo (JIRA)" <ji...@apache.org> on 2018/07/30 14:52:00 UTC
[jira] [Resolved] (SPARK-24581) Design:
BarrierTaskContext.barrier()
[ https://issues.apache.org/jira/browse/SPARK-24581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jiang Xingbo resolved SPARK-24581.
----------------------------------
Resolution: Fixed
> Design: BarrierTaskContext.barrier()
> ------------------------------------
>
> Key: SPARK-24581
> URL: https://issues.apache.org/jira/browse/SPARK-24581
> Project: Spark
> Issue Type: Story
> Components: ML, Spark Core
> Affects Versions: 3.0.0
> Reporter: Xiangrui Meng
> Assignee: Jiang Xingbo
> Priority: Major
>
> We need to provide a communication barrier function to users to help coordinate tasks within a barrier stage. This is very similar to MPI_Barrier function in MPI. This story is for its design.
>
> Requirements:
> * Low-latency. The tasks should be unblocked soon after all tasks have reached this barrier. The latency is more important than CPU cycles here.
> * Support unlimited timeout with proper logging. For DL tasks, it might take very long to converge, we should support unlimited timeout with proper logging. So users know why a task is waiting.
--
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