[
https://issues.apache.org/jira/browse/FLINK-24743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18129209#comment-18129209
]
Martijn Visser commented on FLINK-24743:
----------------------------------------
Still happening, release-1.20 nightly 2026-10-09 (e2e_2_ci, static OpenSSL):
the Dispatcher came up but the TaskManager never registered and shut itself
down after the five-minute registration timeout:
https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=79976&view=logs&j=af184cdd-c6d8-5084-0b69-7e9c67b35f7a
{code}
2026-10-09 02:17:25,807 INFO
org.apache.flink.runtime.taskexecutor.TaskExecutor [] - Could not
resolve ResourceManager address
pekko.ssl.tcp://flink@localhost:6123/user/rpc/resourcemanager_*, retrying in
10000 ms: Could not connect to rpc endpoint under address
pekko.ssl.tcp://flink@localhost:6123/user/rpc/resourcemanager_*.
2026-10-09 02:17:39,074 WARN org.apache.pekko.remote.EndpointReader
[] - Discarding inbound message to
[Actor[pekko://flink/user/rpc/taskmanager_0#-645709897]] in read-only
association to [pekko.ssl.tcp://flink@localhost:6123].
...
2026-10-09 02:22:15,802 ERROR
org.apache.flink.runtime.taskexecutor.TaskExecutor [] - Fatal error
occurred in TaskExecutor
pekko.ssl.tcp://flink@localhost:39805/user/rpc/taskmanager_0.
org.apache.flink.runtime.taskexecutor.exceptions.RegistrationTimeoutException:
Could not register at the ResourceManager within the specified maximum
registration duration PT5M. This indicates a problem with this instance.
Terminating now.
{code}
FLINK-25358 has the same symptom.
> 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, 1.20.6
> Reporter: Till Rohrmann
> Priority: Major
> Labels: auto-deprioritized-major, test-stability
>
> 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.10#820010)