Re: Disable flink old checkpoint clean

Hello, maybe someone can correct me if I'm wrong, but reading through [1], it seems to me that manually triggered checkpoints were meant for these scenarios. If the implementation follows the ticket's description, a user-triggered checkpoint would "break the chain of incremental checkpoints", whic

Re: Flink Job Failed With Kafka Exception

Hi Madan, Perhaps you can filter out inactive topics in the client first and then pass the filtered list of topics to KafkaConsumer. Best, Feng On Tue, Nov 7, 2023 at 10:42 AM Madan D via user wrote: > Hello Hang/Lee, > Thanks! > In my usecase we listen from multiple topics but in few cases o

FlinkDeployment in Kubernetes and JVM parameters —add-opens

Dear Flink Community, I am using Flink 1.18, Java 17 and Flink Kubernetes Operator 1.6.1 to deploy my app in a Kubernetes cluster, using FlinkDeployment CR. When the application starts up I get the error: Caused by: java.lang.RuntimeException: java.lang.reflect.InaccessibleObjectException: Unabl

RE: FlinkDeployment in Kubernetes and JVM parameters —add-opens

Using FLINK_ENV_JAVA_OPTS instead solves the problem. Best, Fourais On 2023/11/08 19:06:43 Rafael Guerrero wrote: > Dear Flink Community, > > I am using Flink 1.18, Java 17 and Flink Kubernetes Operator 1.6.1 to > deploy my app in a Kubernetes cluster, using FlinkDeployment CR. When the > applic

Increasing maximum number of FlinkDeployments that the Operator can handle

Hi Flink Community, This is a follow-up on a previous email thread (see email thread below). After changing the number of operator pods to 1, although we didn't encounter the multiple leaders issue anymore, our singleton operator pod restarts whenever we have 150+ FlinkDeployments. Sometimes, the

Re: Increasing maximum number of FlinkDeployments that the Operator can handle

Currently, 16GB of heap size is allocated to the flink-kubernetes-operator container by setting *jvmArgs.operator*, and this didn't help either. On Wed, Nov 8, 2023 at 5:56 PM Tony Chen wrote: > Hi Flink Community, > > This is a follow-up on a previous email thread (see email thread below). > Af

Flink-1.18 mvn test error

Dear Flink Community, I am using Java 1.8.0_ 202 and Maven 3.8.8 build Flink 1.18, but encountered an error ： ``` [ERROR] Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:3.2.0:copy-dependencies (copy-dependencies) on project flink-clients: Artifact has not been packaged

Distributed cache support in async io

Hi all, I noticed distributed cache is not supported in async io, is there any reason for that? It's understandable that state apis are not supported since the data might be changed in working threads. But I don't know why distributed cache is not supported either. org.apache.flink.streaming.api.