You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Dongjoon Hyun (JIRA)" <ji...@apache.org> on 2019/05/29 22:00:00 UTC

[jira] [Resolved] (SPARK-27868) Better document shuffle / RPC listen backlog

     [ https://issues.apache.org/jira/browse/SPARK-27868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dongjoon Hyun resolved SPARK-27868.
-----------------------------------
       Resolution: Fixed
         Assignee: Marcelo Vanzin
    Fix Version/s: 3.0.0
                   2.4.4

This is resolved via https://github.com/apache/spark/pull/24732

> Better document shuffle / RPC listen backlog
> --------------------------------------------
>
>                 Key: SPARK-27868
>                 URL: https://issues.apache.org/jira/browse/SPARK-27868
>             Project: Spark
>          Issue Type: Bug
>          Components: Documentation, Spark Core
>    Affects Versions: 2.4.3
>            Reporter: Marcelo Vanzin
>            Assignee: Marcelo Vanzin
>            Priority: Minor
>             Fix For: 2.4.4, 3.0.0
>
>
> The option to control the listen socket backlog for RPC and shuffle servers is not documented in our public docs.
> The only piece of documentation is in a Java class, and even that documentation is incorrect:
> {code}
>   /** Requested maximum length of the queue of incoming connections. Default -1 for no backlog. */
>   public int backLog() { return conf.getInt(SPARK_NETWORK_IO_BACKLOG_KEY, -1); }
> {code}
> The default value actual causes the default value from the JRE to be used, which is 50 according to the docs.



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