You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Ferenc Csaky (Jira)" <ji...@apache.org> on 2024/10/15 07:10:00 UTC

[jira] [Commented] (FLINK-36533) An exception occurs when using the taskmanager.data.bind-port

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

Ferenc Csaky commented on FLINK-36533:
--------------------------------------

We hit the same issue described in SPARK-18383. In case of "epoll" Netty transport (which is a Linux-only feature), Netty uses different sockets and throws a different exception type in case of a used address. Will raise a PR shortly.

> An exception occurs when using the taskmanager.data.bind-port
> -------------------------------------------------------------
>
>                 Key: FLINK-36533
>                 URL: https://issues.apache.org/jira/browse/FLINK-36533
>             Project: Flink
>          Issue Type: Bug
>    Affects Versions: 1.20.0, 1.19.1, 2.0-preview
>            Reporter: five
>            Assignee: Ferenc Csaky
>            Priority: Major
>             Fix For: 2.0.0, 1.19.2, 1.20.1
>
>         Attachments: exception.png, source_code.png
>
>
> An error occurred when using a port range for the {{taskmanager.data.bind-port}} configuration item.
>  
> Environment Information:
>  * Flink version: 1.20.0
>  * Java: 1.8
> Configuration Information:
>  * taskmanager.data.bind-port: 12001-13000
> When starting the Flink job, an exception occurs. Please see the attached file for the exception message: exception.png
> The error received is a NativeIoException. However, the source code is set up to catch a BindException. (Refer to the attached file: source_code.png) The two do not match.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)