[
https://issues.apache.org/jira/browse/FLINK-23030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-23030:
-----------------------------------
Labels: pull-request-available stale-blocker (was: pull-request-available)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as a
Blocker but is unassigned and neither itself nor its Sub-Tasks have been
updated for 1 days. I have gone ahead and marked it "stale-blocker". If this
ticket is a Blocker, please either assign yourself or give an update.
Afterwards, please remove the label or in 7 days the issue will be
deprioritized.
> PartitionRequestClientFactory#createPartitionRequestClient should throw when
> network failure
> --------------------------------------------------------------------------------------------
>
> Key: FLINK-23030
> URL: https://issues.apache.org/jira/browse/FLINK-23030
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Network
> Reporter: Jin Xing
> Priority: Blocker
> Labels: pull-request-available, stale-blocker
>
> In current _PartitionRequestClientFactory#createPartitionRequestClient_,
> _ChannelFuture#await()_ is invoked, thus to build a connection to remote
> synchronously.
> But with the doc of _io.netty.util.concurrent.Future_ [1] and its
> implementation _io.netty.channel.DefaultChannelPromise_ [2],
> _ChannelFuture#await()_ never throws when completed with failure. I guess
> what Flink needs is _ChannelFuture#sync()._
> [1] [https://netty.io/4.1/api/io/netty/util/concurrent/class-use/Future.html]
> [2]
> [https://github.com/netty/netty/blob/4.1/transport/src/main/java/io/netty/channel/DefaultChannelPromise.java]
>
> https://github.com/netty/netty/blob/4.1/common/src/main/java/io/netty/util/concurrent/DefaultPromise.java
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
