Re: [External] Regarding java.lang.IllegalStateException

My guess it’s a major known issue. Need a workaround. https://issues.apache.org/jira/browse/FLINK-32212 /Maxim From: prashant parbhane Date: Tuesday, April 23, 2024 at 11:09 PM To: user@flink.apache.org Subject: [External] Regarding java.lang.IllegalStateException Hello, We have been facing

Re: [External] Exception during autoscaling operation - Flink 1.18/Operator 1.8.0

I was talking about Flink Kubernetes operator and HA , not the individual Flink jobs. But based on your answer it’s probably not the cause Gyula On Fri, 26 Apr 2024 at 21:15, Maxim Senin wrote: > Hi, Gyula. Thanks for the tips. > > All jobs are deployed in a single namespace, “flink”. > >

Re: [External] Exception during autoscaling operation - Flink 1.18/Operator 1.8.0

Here’s more detail on the UnsupportedOperation exception. The job starts, operator collects some stats and then the job dies, apparently on rescaling op: [INFO ][flink/f-d7681d0f-c093-5d8a-b5f5-2b66b4547bf6] >>> Event | Info| JOBSTATUSCHANGED | Job status changed from CREATED to RUNNING

Re: Regarding java.lang.IllegalStateException

We are also seeing something similar: 2024-04-26 16:30:44,401 INFO org.apache.flink.runtime.executiongraph.ExecutionGraph [] - Source: Power Consumption:power_consumption -> Ingest Power Consumption -> PopSysFields -> WindowingWatermarkPreCheck (1/1)

Re: [External] Exception during autoscaling operation - Flink 1.18/Operator 1.8.0

Hi, Gyula. Thanks for the tips. All jobs are deployed in a single namespace, “flink”. Which replicas? The JM replicas are already 1, I tried with TM replicas set to 1, but same exception happens. We have only 1 instance of the operator (replicas=1) in this environment. The only workarounds I

Re: Strange Problem (0 AvailableTask)

Hi Biao, Thanks for your reply, fortunately the problem is solved. All I did was changed the bind-host to 0.0.0.0 (previously it was set to the server's IP). I don't know if it's best practice or not but everything is working fine now. RIght now I am using flink as standalone (I have the

Re: Flink SQL Client does not start job with savepoint

Hi Lee, A quick question: what version of flink are you using for testing execution.state-recovery.path? It looks like this config is only supported in flink 1.20 which is not released yet. Best, Biao Geng Lee, Keith 于2024年4月26日周五 04:51写道：

Re: Strange Problem (0 AvailableTask)

Hi Hemi, How do you start your flink cluster? Are you using standalone cluster or using k8s/yarn as resource providers? Also, it would be very helpful if you can share the full jobmanager log. Best, Biao Geng Hemi Grs 于2024年4月18日周四 15:43写道： > Hello, > > I have several versions of Flink

Re: [External] Exception during autoscaling operation - Flink 1.18/Operator 1.8.0

Hi Maxim! Regarding the status update error, it could be related to a problem that we have discovered recently with the Flink Operator HA. Where during a namespace change both leader and follower instances would start processing. It has been fixed in the current master by updating the JOSDK

Re: Async code inside Flink Sink

Hi Jacob, For your first question, I think it is fine to use Java completableFuture for your case. If we create lots of threads, of course it would consume more CPU and influent the processing of records. But in your case, the close op may not be very heavy. One thing comes to mind is that when