Hi It seems your job did not connect the kafka correctly or the network between your cluster and kafka is unreachable. I think you can get detailed information from log or check the network
Best, Shammon FY On Sat, Apr 15, 2023 at 3:37 AM Lampros Makrodimitris <[email protected]> wrote: > Hi community, > > I am pretty new to the Flink ecosystem and I am trying to create a Flink > consumer that consumes messages from an Azure Event Hub for Apache Kafka. > My flink job runs on an ubuntu vm. > > When I run my job via the mvn -exec command the consumer brings messages. > > Following a different process, where I start a standalone cluster (via > start-cluster.sh), then packaging my code to a .jar file and submitting the > job by using the command flink run, I get the following message: > > INFO org.apache.kafka.clients.admin.internals.AdminMetadataManager [] - > [AdminClient clientId=flink-consumer-enumerator-admin-client] Metadata > update failed > org.apache.kafka.common.errors.TimeoutException: > Call(callName=fetchMetadata, deadlineMs=1680868187237, tries=1, > nextAllowedTryMs=1680868187367) timed out at 1680868187267 after 1 > attempt(s) > Caused by: org.apache.kafka.common.errors.DisconnectException: Cancelled > fetchMetadata request with correlation id 4 due to node 0 being disconnected > > I think that the main reason behind the failure has something to do with > the configurations of the cluster that I start, as defined at conf.yaml, > since the mvn -exec runs it locally. > > Any proposal, suggestion or guide is welcome guide. > > Regards, > Lampros > >
