Hi Hang,
Few more points regarding this issue
1. The issue does not replicate in my local installation and occurs only on
kubernetes server installation.
2. We have used kubernetes operator to install flink on the server
Please let me know if any other info is required here.
Thanks,
Tauseef
On
Hi Hang,
I cross checked this issue multiple times. I also upgraded to flink 1.18
but the issue persists.
Can you please let me know a few guidelines on how to investigate this and
fix it positively.
Thanks,
Tauseef
On Thu, 23 Nov 2023 at 18:08, Tauseef Janvekar
wrote:
> Thanks Hang.
>
> I go
Thanks Hang.
I got it now. I will check on this and get back to you.
Thanks,
Tauseef.
On Thu, 23 Nov 2023 at 17:29, Hang Ruan wrote:
> Hi, Tauseef.
>
> This error is not that you can not access the Kafka cluster. Actually,
> this error means that the JM cannot access its TM.
> Have you ever ch
Hi, Tauseef.
This error is not that you can not access the Kafka cluster. Actually, this
error means that the JM cannot access its TM.
Have you ever checked whether the JM is able to access the TM?
Best,
Hang
Tauseef Janvekar 于2023年11月23日周四 16:04写道：
> Dear Team,
>
> We are facing the below iss
Dear Team,
We are facing the below issue while connecting to confluent kafka
Can someone please help here.
2023-11-23 06:09:36,989 INFO org.apache.flink.runtime.executiongraph.
ExecutionGraph [] - Source: src_source -> Sink: Print to Std. Out (1/1)
(496f859d5379cd751a3fc473625125f3_cbc357c
