Re: [E] Re: Kubernetes operator expose UI rest service as NodePort instead of default clusterIP

Jacob, Thanks, I checked it out and didn't work. The config overriding to ClusterIP part

What is the recommended solution for this error of too many files open during a checkpoint?

What is the recommended solution for this error of too many files open during a checkpoint? 2022-09-02 10:04:56 java.io.IOException: Could not perform checkpoint 119366 for operator tag enrichment (3/4)#104. at org.apache.flink.streaming.runtime.tasks.StreamTask.triggerCheckpointOnBarrier(Strea

RE: Re: [DISCUSS] Contribution of Multi Cluster Kafka Source

Hi Mason, First off, thanks for putting this FLIP together! Sorry for the delay. Full disclosure Mason and I chatted a little bit at Flink Forward 2022 but I have tried to capture the questions I had for him then. I'll start the conversation with a few questions: 1. The concept of streamIds is n

Re: [E] Re: Kubernetes operator expose UI rest service as NodePort instead of default clusterIP

I remember testing the operator with the rest service exposed as NodePort. NodePort requires rbac.nodeRoules.create: true (default is false) in values.yaml. Maybe you missed that? https://github.com/apache/flink-kubernetes-operator/blob/release-1.1/helm/flink-kubernetes-operator/values.yaml#L34-L3

Re: flink ci build run longer than the maximum time of 310 minutes.

Not sure whether that applies to your case, but there was a recent issue [1] where the e2e_1_ci job ran into a timeout. If that's what you were observing, rebasing your branch might help. Best, Matthias [1] https://issues.apache.org/jira/browse/FLINK-29161 On Fri, Sep 2, 2022 at 10:51 AM Martijn

Re: Kafka source stops consuming messages from topic after some minutes

My initial thought is that there's something in your business logic. You're reading from one Kafka topic, then you're mentioning that it's "connected" to another Kafka topic. What type of business logic are you executing? Are you joining data, looking things up etc? My suspicion would be that in th

Re: flink ci build run longer than the maximum time of 310 minutes.

You can ask the Flinkbot to run again by typing as comment @flinkbot run azure Best regards, Martijn Op vr 2 sep. 2022 om 08:40 schreef hjw <1010445...@qq.com>: > I commit a pr to Flink Github . > A error happened in building ci. > [error]The job running on agent Azure Pipelines 6 ran longer t