[
https://issues.apache.org/jira/browse/FLINK-10177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16913127#comment-16913127
]
Nico Kruber commented on FLINK-10177:
-------------------------------------
One thing to consider/test: if, for whatever reason one TM would end up with
NIO and another with epoll, they should theoretically work together but this
should be verified. After all, this is just the local channel listening
implementation.
On the other hand, most deployments should be homogeneous and therefore not end
up in that scenario.
> Use network transport type AUTO by default
> ------------------------------------------
>
> Key: FLINK-10177
> URL: https://issues.apache.org/jira/browse/FLINK-10177
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Configuration, Runtime / Network
> Affects Versions: 1.6.0, 1.7.0
> Reporter: Nico Kruber
> Assignee: boshu Zheng
> Priority: Major
>
> Now that the shading issue with the native library is fixed (FLINK-9463),
> EPOLL should be available on (all?) Linux distributions and provide some
> efficiency gain (if enabled). Therefore,
> {{taskmanager.network.netty.transport}} should be set to {{auto}} by default.
> If EPOLL is not available, it will automatically fall back to NIO which
> currently is the default.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
