[
https://issues.apache.org/jira/browse/FLINK-24743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17496064#comment-17496064
]
Chesnay Schepler commented on FLINK-24743:
------------------------------------------
I don't think we can do anything about this for now.
Changing {{use-passive-connections}} is not something that I'd be comfortable
with, because that would change how the Flink processes setup connections with
each other, and god knows what that will break.
Upgrading to Artery is probably the best approach, and I had looking into that
on my to-do list already (and I could've sworn that there was a ticket for
that...).
> New File Sink end-to-end test fails on Azure
> --------------------------------------------
>
> Key: FLINK-24743
> URL: https://issues.apache.org/jira/browse/FLINK-24743
> Project: Flink
> Issue Type: Bug
> Components: Connectors / FileSystem, Runtime / Coordination, Tests
> Affects Versions: 1.15.0
> Reporter: Till Rohrmann
> Priority: Critical
> Labels: test-stability
> Fix For: 1.15.0
>
>
> The {{New File Sink end-to-end test}} fails on Azure. It seems that the
> {{TaskExecutor}} cannot connect with the {{ResourceManager}} because
> {{Discarding inbound message to
> [Actor[akka://flink/user/rpc/taskmanager_0#1155592017]] in read-only
> association to [akka.ssl.tcp://flink@localhost:6123]. If this happens often
> you may consider using akka.remote.use-passive-connections=off or use Artery
> TCP.}}
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=25831&view=logs&j=c88eea3b-64a0-564d-0031-9fdcd7b8abee&t=070ff179-953e-5bda-71fa-d6599415701c&l=11674
> cc [~chesnay], this might be related to the recent Akka bump.
> Related: https://github.com/akka/akka/issues/24393
> Maybe we should upgrade to using Artery TCP or set
> {{akka.remote.use-passive-connections=off}}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
