You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Nishkam Ravi (JIRA)" <ji...@apache.org> on 2015/06/01 04:43:17 UTC

[jira] [Commented] (SPARK-7988) Mechanism to control receiver scheduling

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

Nishkam Ravi commented on SPARK-7988:
-------------------------------------

Receiver.preferredLocation already helps to some extent. For this feature, we could modify streaming.scheduler.startReceivers() to populate  preferredLocation value for each receiver (if empty) by iterating over the list of executors (for the round-robin scheme for example) ?

> Mechanism to control receiver scheduling 
> -----------------------------------------
>
>                 Key: SPARK-7988
>                 URL: https://issues.apache.org/jira/browse/SPARK-7988
>             Project: Spark
>          Issue Type: New Feature
>          Components: Streaming
>            Reporter: Nishkam Ravi
>            Priority: Minor
>
> Streaming receivers are currently scheduled by the underlying Spark scheduler in the same way as other tasks. Will help performance if we added a knob to control receiver scheduling. In most cases, even distribution of receivers among workers should yield best results. In some cases, dense scheduling (e.g, all receivers on one node) may perform better. Maybe support for a new configuration parameter spark.receiver.scheduling.mode (or some such) would help. With 'default' as the current scheduling scheme and 'round-robin' for even distribution among workers (and potentially a third mode for 'dense' scheduling).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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