Re: kafka sink
Hi nick, Is there any error log? That may help to analyze the root cause. On Sun, Jul 23, 2023 at 9:53 PM nick toker wrote: > hello > > > we replaced deprecated kafka producer with kafka sink > and from time to time when we submit a job he stack for 5 min in > inisazaing ( on sink operators) > we verify the the transaction prefix is unique > > it's not happened when we use kafka producer > > What can be the reason? > >
Re: Set processing time in the past
Hi, Eugenio Can you describe the requirements in more detail? Best, Ron Shammon FY 于2023年7月17日周一 09:10写道： > Hi Eugenio, > > I cannot catch it clearly, could you describe it in more detail? > > Best, > Shammon FY > > On Sat, Jul 15, 2023 at 5:14 PM Eugenio Marotti < > ing.eugenio.maro...@gmail.com> wrote: > >> Hi everyone, >> >> is there a way to set Flink processing time in the past? >> >> Thanks >> Eugenio >> >
Re: flink1.17.1版本 MiniCluster is not yet running or has already been shut down.
Hi, 运行的是哪个例子？从错误上看是在从MiniCluster获取结果的时候，MiniCluster被关闭了 Best, Shammon FY On Sat, Jul 22, 2023 at 3:25 PM guanyq wrote: > 本地IDEA运行 MiniCluster is not yet running or has already been shut down. > 请问是什么原因，如何处理 > > > > > 15:19:27,511 INFO > org.apache.flink.runtime.resourcemanager.ResourceManagerServiceImpl [] - > Stopping resource manager service. > > 15:19:27,503 WARN > org.apache.flink.streaming.api.operators.collect.CollectResultFetcher [] - > Failed to get job status so we assume that the job has terminated. Some > data might be lost. > > java.lang.IllegalStateException: MiniCluster is not yet running or has > already been shut down. > > at org.apache.flink.util.Preconditions.checkState(Preconditions.java:193) > ~[flink-core-1.17.1.jar:1.17.1] > > at > org.apache.flink.runtime.minicluster.MiniCluster.getDispatcherGatewayFuture(MiniCluster.java:1060) > ~[flink-runtime-1.17.1.jar:1.17.1] > > at > org.apache.flink.runtime.minicluster.MiniCluster.runDispatcherCommand(MiniCluster.java:933) > ~[flink-runtime-1.17.1.jar:1.17.1] > > at > org.apache.flink.runtime.minicluster.MiniCluster.getJobStatus(MiniCluster.java:857) > ~[flink-runtime-1.17.1.jar:1.17.1] > > at > org.apache.flink.runtime.minicluster.MiniClusterJobClient.getJobStatus(MiniClusterJobClient.java:91) > ~[flink-runtime-1.17.1.jar:1.17.1] > > at > org.apache.flink.streaming.api.operators.collect.CollectResultFetcher.isJobTerminated(CollectResultFetcher.java:210) > [flink-streaming-java-1.17.1.jar:1.17.1] > > at > org.apache.flink.streaming.api.operators.collect.CollectResultFetcher.next(CollectResultFetcher.java:118) > [flink-streaming-java-1.17.1.jar:1.17.1] > > at > org.apache.flink.streaming.api.operators.collect.CollectResultIterator.nextResultFromFetcher(CollectResultIterator.java:106) > [flink-streaming-java-1.17.1.jar:1.17.1] > > at > org.apache.flink.streaming.api.operators.collect.CollectResultIterator.hasNext(CollectResultIterator.java:80) > [flink-streaming-java-1.17.1.jar:1.17.1] > > at > org.apache.flink.table.planner.connectors.CollectDynamicSink$CloseableRowIteratorWrapper.hasNext(CollectDynamicSink.java:222) > [flink-table-planner_25e35ab8-6377-4c6a-a928-a9fe1ff9e7f4.jar:1.17.1] > > at > org.apache.flink.table.utils.print.TableauStyle.print(TableauStyle.java:120) > [flink-table-common-1.17.1.jar:1.17.1] > > at > org.apache.flink.table.api.internal.TableResultImpl.print(TableResultImpl.java:153) > [flink-table-api-java-1.17.1.jar:1.17.1]
RE: TCP server socket with Kubernetes Cluster
Hello Community, Please share views for below mail. Rgds, Kamal From: Kamal Mittal via user Sent: 21 July 2023 02:02 PM To: user@flink.apache.org Subject: TCP server socket with Kubernetes Cluster Hello, Created a TCP server socket single source function and it is opened on a single POD (taskmanager) of Kubernetes cluster out of a set of PODs (taskmanager) by Flink. Is there any way to know on which POD (taskmanager) it is opened? Does Flink gives any such information? This is needed for client to access the same POD Kubernetes service. Rgds, Kamal
kafka sink
hello we replaced deprecated kafka producer with kafka sink and from time to time when we submit a job he stack for 5 min in inisazaing ( on sink operators) we verify the the transaction prefix is unique it's not happened when we use kafka producer What can be the reason?
退订
退订
