Hi Peter, thanks for sharing. That doesn't sound right. May you provide the entire jobmanager logs?
Best, Matthias On Thu, Apr 21, 2022 at 6:08 PM Peter Schrott <pe...@bluerootlabs.io> wrote: > Hi Flink-Users, > > I am not sure if this does something to my cluster or not. But since > updating to Flink 1.15 (atm rc4) I find the following logs: > > INFO: Registering job manager ab7db9ff0ebd26b3b89c3e2e56684...@akka.tcp:// > fl...@flink-jobmanager-xxx.com:40015/user/rpc/jobmanager_2 for job > 5566648d9b1aac6c1a1b78187fd56975. > > as many times as number of parallelisms (here 10 times). These logs are > triggered every 5 minutes. > > Then they are followed by: > > INFO: Registration of job manager ab7db9ff0ebd26b3b89c3e2e56684762 > @akka.tcp://fl...@flink-jobmanager-xxx.com:40015/user/rpc/jobmanager_2 > failed. > > also 10 log entries. > > I followed the lifetime of the job (5566648d9b1aac6c1a1b78187fd56975), it > was a long-running sql streaming job, started on Apr 13th on a standalone > cluster. After some recovery attempts it finally failed (using the failover > strategy) on the 20th Apr (yesterday) for good. Then those logs started to > appear. Now there was no other job running on my cluster anymore but the > logs appeared every 5 minutes until I restarted this jobmanager service. > > This job was just an example, it happens to other jobs too. > > It's just INFO logs but it does not look healthy either. > > Thanks & Best > Peter >
