[jira] [Resolved] (SPARK-18383) Utils.isBindCollision does not properly handle all possible address-port collisions when binding

["Sean Owen (JIRA)" <ji...@apache.org>]

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

Sean Owen resolved SPARK-18383.
-------------------------------
       Resolution: Fixed
    Fix Version/s: 2.1.0

Issue resolved by pull request 15830
[https://github.com/apache/spark/pull/15830]

> Utils.isBindCollision does not properly handle all possible address-port collisions when binding
> ------------------------------------------------------------------------------------------------
>
>                 Key: SPARK-18383
>                 URL: https://issues.apache.org/jira/browse/SPARK-18383
>             Project: Spark
>          Issue Type: Bug
>          Components: Spark Core
>    Affects Versions: 1.6.2, 2.0.1
>            Reporter: Guoqiang Li
>             Fix For: 2.1.0
>
>
> When the IO mode is set to epoll, Netty uses {{io.netty.channel.unix.Socket}} class, and {{Socket.bind}}  throws an exception that is a {{io.netty.channel.unix.Errors.NativeIoException}}  instead of a {{java.net.BindException}} instance



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