Re: how to reduce read times when many jobs read the same kafka topic?

Thanks for you explanation. I'll give it a try. :) Sachin Mittal 于2024年5月15日周三 10:39写道： > Each separate job would have its own consumer group hence they will read > independently from the same topic and when checkpointing they will commit > their own offsets. > So if any job fails, it will not a

Re: how to reduce read times when many jobs read the same kafka topic?

Each separate job would have its own consumer group hence they will read independently from the same topic and when checkpointing they will commit their own offsets. So if any job fails, it will not affect the progress of other jobs when reading from Kafka. I am not sure of the impact of network l

how to reduce read times when many jobs read the same kafka topic?

hi there are many flink jobs read one kafka topic in this scenario, therefore CPU resources waste in serialization/deserialization and network load is too heavy . Can you recommend a solution to avoid this situation? e.g it can be more effectively using one large stream job with multi branchs ?