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
Hello Hang/Lee,Thanks!In my usecase we listen from multiple topics but in few cases one of the topic may become inactive if producer decides to shutdown one of the topic but other topics still will be receiving data but what we observe is that if there’s one of the topic is getting in-active entire
Hi, Madan.
This error seems like that there are some problems when the consumer tries
to read the topic metadata. If you use the same source for these topics,
the kafka connector cannot skip one of them. As you say, you need to modify
the connector's default behavior.
Maybe you should read the cod
Hi Madan,
Do you mean you want to restart only the failed tasks, rather than
restarting the entire pipeline region? As far as I know, currently Flink
does not support task-level restart, but requires restarting the pipeline
region.
Best,
Junrui
Madan D via user 于2023年10月11日周三 12:37写道：
> Hello
Hello Team, We are running the Flink pipeline by consuming data from multiple
topics, but we recently encountered that if there's one topic having issues
with participation, etc., the whole Flink pipeline is failing, which is
affecting topics. Is there a way we can make Flink Piplein keep runnin
