Hi Dominik
Setting that bit of configuration seems to have done the trick for the
MXBean exception.
Many thanks for your help.
Best regards,
Mark
On Tue, 23 Oct 2018 at 14:41, Dominik Wosiński wrote:
> Hey Mark,
>
> Do You use more than 1 Kafka consumer for Your jobs? I think this relates
>
Hey Mark,
Do You use more than 1 Kafka consumer for Your jobs? I think this relates
to the known issue in Kafka:
https://issues.apache.org/jira/browse/KAFKA-3992.
The problem is that if You don't provide client ID for your
*KafkaConsumer* Kafka
assigns one, but this is done in an unsynchronized
Hi,
We regularly see the following two exceptions in a number of jobs shortly
after they have been resumed during our flink cluster startup:
org.apache.kafka.common.KafkaException: Error registering mbean
kafka.consumer:type=consumer-node-metrics,client-id=consumer-1,node-id=node--1
at
