This could be a bug in Kafkas JmxReporter class: https://issues.apache.org/jira/browse/KAFKA-6307

On 07.02.2018 13:37, Edward wrote:
We are using FlinkKafkaConsumer011 and FlinkKafkaProducer011, but we also
experienced the same behavior with FlinkKafkaConsumer010 and
FlinkKafkaProducer010.



--
Sent from: http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/


Reply via email to