Re: Flink pending record metric weired after autoscaler rescaling

Yes, https://issues.apache.org/jira/browse/FLINK-34063 does match quite well the issues I have encountered. I'll leave a comment in that ticket then. Thanks, Yang On Fri, 12 Jan 2024 at 15:39, Gyula Fóra wrote: > Could this be related to the

Re: Flink pending record metric weired after autoscaler rescaling

Could this be related to the issue reported here? https://issues.apache.org/jira/browse/FLINK-34063 Gyula On Wed, Jan 10, 2024 at 4:04 PM Yang LI wrote: > Just to give more context, my setup uses Apache Flink 1.18 with the > adaptive scheduler enabled, issues happen randomly particularly >

Re: Flink pending record metric weired after autoscaler rescaling

Just to give more context, my setup uses Apache Flink 1.18 with the adaptive scheduler enabled, issues happen randomly particularly post-restart behaviors. After each restart, the system logs indicate "Adding split(s) to reader:", signifying the reassignment of partitions across different

Flink pending record metric weired after autoscaler rescaling

Dear Flink Community, I've encountered an issue during the testing of my Flink autoscaler. It appears that Flink is losing track of specific Kafka partitions, leading to a persistent increase in lag on these partitions. The logs indicate a 'kafka connector metricGroup name collision exception.'