[
https://issues.apache.org/jira/browse/FLINK-8093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17397961#comment-17397961
]
João Boto edited comment on FLINK-8093 at 8/12/21, 10:11 AM:
-------------------------------------------------------------
we are getting this error on standalone clusters in version 1.12.2 and 1.13.1
(kafka library 2.4, kafka cluster 2.2)
plus this is making that blobStore directories dont be cleaned up
in our case the error is this:
{code:java}
11:37:21.670 [kafka-producer-network-thread | producer-1] ERROR
org.apache.kafka.common.metrics.Metrics - Error when removing metric from
org.apache.kafka.common.metrics.JmxReporter
org.apache.kafka.common.KafkaException: Error registering mbean
kafka.producer:type=producer-node-metrics,client-id=producer-1,node-id=node-1
at
org.apache.kafka.common.metrics.JmxReporter.reregister(JmxReporter.java:170)
~[blob_p-a919a773598709e09d23acb437d28be4e1388a1e-8eb08e34806bcbe55903d599feb0a0f4:?]
at
org.apache.kafka.common.metrics.JmxReporter.metricRemoval(JmxReporter.java:101)
~[blob_p-a919a773598709e09d23acb437d28be4e1388a1e-8eb08e34806bcbe55903d599feb0a0f4:?]
at
org.apache.kafka.common.metrics.Metrics.removeMetric(Metrics.java:534)
[blob_p-a919a773598709e09d23acb437d28be4e1388a1e-8eb08e34806bcbe55903d599feb0a0f4:?]
at
org.apache.kafka.common.metrics.Metrics.removeSensor(Metrics.java:448)
[blob_p-a919a773598709e09d23acb437d28be4e1388a1e-8eb08e34806bcbe55903d599feb0a0f4:?]
at
org.apache.kafka.common.network.Selector$SelectorMetrics.close(Selector.java:1237)
[blob_p-a919a773598709e09d23acb437d28be4e1388a1e-8eb08e34806bcbe55903d599feb0a0f4:?]
at org.apache.kafka.common.utils.Utils.closeQuietly(Utils.java:844)
[blob_p-a919a773598709e09d23acb437d28be4e1388a1e-8eb08e34806bcbe55903d599feb0a0f4:?]
at org.apache.kafka.common.network.Selector.close(Selector.java:373)
[blob_p-a919a773598709e09d23acb437d28be4e1388a1e-8eb08e34806bcbe55903d599feb0a0f4:?]
at org.apache.kafka.clients.NetworkClient.close(NetworkClient.java:639)
[blob_p-a919a773598709e09d23acb437d28be4e1388a1e-8eb08e34806bcbe55903d599feb0a0f4:?]
at
org.apache.kafka.clients.producer.internals.Sender.run(Sender.java:287)
[blob_p-a919a773598709e09d23acb437d28be4e1388a1e-8eb08e34806bcbe55903d599feb0a0f4:?]
at java.lang.Thread.run(Thread.java:834) [?:?]
Caused by: javax.management.InstanceAlreadyExistsException:
kafka.producer:type=producer-node-metrics,client-id=producer-1,node-id=node-1
at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:436)
~[?:?]
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerWithRepository(DefaultMBeanServerInterceptor.java:1855)
~[?:?]
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:955)
~[?:?]
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:890)
~[?:?]
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:320)
~[?:?]
at
com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:522)
~[?:?]
at
org.apache.kafka.common.metrics.JmxReporter.reregister(JmxReporter.java:168)
~[blob_p-a919a773598709e09d23acb437d28be4e1388a1e-8eb08e34806bcbe55903d599feb0a0f4:?]
... 9 more
{code}
was (Author: eskabetxe):
we are getting this error on standalone clusters in version 1.12.2 and 1.13.1
plus this is making that blobStore directories dont be cleaned up
in our case the error is this:
{code:java}
11:37:21.670 [kafka-producer-network-thread | producer-1] ERROR
org.apache.kafka.common.metrics.Metrics - Error when removing metric from
org.apache.kafka.common.metrics.JmxReporter
org.apache.kafka.common.KafkaException: Error registering mbean
kafka.producer:type=producer-node-metrics,client-id=producer-1,node-id=node-1
at
org.apache.kafka.common.metrics.JmxReporter.reregister(JmxReporter.java:170)
~[blob_p-a919a773598709e09d23acb437d28be4e1388a1e-8eb08e34806bcbe55903d599feb0a0f4:?]
at
org.apache.kafka.common.metrics.JmxReporter.metricRemoval(JmxReporter.java:101)
~[blob_p-a919a773598709e09d23acb437d28be4e1388a1e-8eb08e34806bcbe55903d599feb0a0f4:?]
at
org.apache.kafka.common.metrics.Metrics.removeMetric(Metrics.java:534)
[blob_p-a919a773598709e09d23acb437d28be4e1388a1e-8eb08e34806bcbe55903d599feb0a0f4:?]
at
org.apache.kafka.common.metrics.Metrics.removeSensor(Metrics.java:448)
[blob_p-a919a773598709e09d23acb437d28be4e1388a1e-8eb08e34806bcbe55903d599feb0a0f4:?]
at
org.apache.kafka.common.network.Selector$SelectorMetrics.close(Selector.java:1237)
[blob_p-a919a773598709e09d23acb437d28be4e1388a1e-8eb08e34806bcbe55903d599feb0a0f4:?]
at org.apache.kafka.common.utils.Utils.closeQuietly(Utils.java:844)
[blob_p-a919a773598709e09d23acb437d28be4e1388a1e-8eb08e34806bcbe55903d599feb0a0f4:?]
at org.apache.kafka.common.network.Selector.close(Selector.java:373)
[blob_p-a919a773598709e09d23acb437d28be4e1388a1e-8eb08e34806bcbe55903d599feb0a0f4:?]
at org.apache.kafka.clients.NetworkClient.close(NetworkClient.java:639)
[blob_p-a919a773598709e09d23acb437d28be4e1388a1e-8eb08e34806bcbe55903d599feb0a0f4:?]
at
org.apache.kafka.clients.producer.internals.Sender.run(Sender.java:287)
[blob_p-a919a773598709e09d23acb437d28be4e1388a1e-8eb08e34806bcbe55903d599feb0a0f4:?]
at java.lang.Thread.run(Thread.java:834) [?:?]
Caused by: javax.management.InstanceAlreadyExistsException:
kafka.producer:type=producer-node-metrics,client-id=producer-1,node-id=node-1
at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:436)
~[?:?]
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerWithRepository(DefaultMBeanServerInterceptor.java:1855)
~[?:?]
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:955)
~[?:?]
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:890)
~[?:?]
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:320)
~[?:?]
at
com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:522)
~[?:?]
at
org.apache.kafka.common.metrics.JmxReporter.reregister(JmxReporter.java:168)
~[blob_p-a919a773598709e09d23acb437d28be4e1388a1e-8eb08e34806bcbe55903d599feb0a0f4:?]
... 9 more
{code}
> flink job fail because of kafka producer create fail of
> "javax.management.InstanceAlreadyExistsException"
> ---------------------------------------------------------------------------------------------------------
>
> Key: FLINK-8093
> URL: https://issues.apache.org/jira/browse/FLINK-8093
> Project: Flink
> Issue Type: Bug
> Components: Connectors / Kafka
> Affects Versions: 1.3.2, 1.10.0
> Environment: flink 1.3.2, kafka 0.9.1
> Reporter: dongtingting
> Priority: Minor
> Labels: auto-deprioritized-critical, auto-deprioritized-major,
> auto-unassigned, usability
>
> one taskmanager has multiple taskslot, one task fail because of create
> kafkaProducer fail，the reason for create kafkaProducer fail is
> “javax.management.InstanceAlreadyExistsException:
> kafka.producer:type=producer-metrics,client-id=producer-3”。 the detail trace
> is ：
> {noformat}
> 2017-11-04 19:41:23,281 INFO org.apache.flink.runtime.taskmanager.Task
> - Source: Custom Source -> Filter -> Map -> Filter -> Sink:
> dp_client_**_log (7/80) (99551f3f892232d7df5eb9060fa9940c) switched from
> RUNNING to FAILED.
> org.apache.kafka.common.KafkaException: Failed to construct kafka producer
> at
> org.apache.kafka.clients.producer.KafkaProducer.<init>(KafkaProducer.java:321)
> at
> org.apache.kafka.clients.producer.KafkaProducer.<init>(KafkaProducer.java:181)
> at
> org.apache.flink.streaming.connectors.kafka.FlinkKafkaProducerBase.getKafkaProducer(FlinkKafkaProducerBase.java:202)
> at
> org.apache.flink.streaming.connectors.kafka.FlinkKafkaProducerBase.open(FlinkKafkaProducerBase.java:212)
> at
> org.apache.flink.api.common.functions.util.FunctionUtils.openFunction(FunctionUtils.java:36)
> at
> org.apache.flink.streaming.api.operators.AbstractUdfStreamOperator.open(AbstractUdfStreamOperator.java:111)
> at
> org.apache.flink.streaming.runtime.tasks.StreamTask.openAllOperators(StreamTask.java:375)
> at
> org.apache.flink.streaming.runtime.tasks.StreamTask.invoke(StreamTask.java:252)
> at org.apache.flink.runtime.taskmanager.Task.run(Task.java:702)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.apache.kafka.common.KafkaException: Error registering mbean
> kafka.producer:type=producer-metrics,client-id=producer-3
> at
> org.apache.kafka.common.metrics.JmxReporter.reregister(JmxReporter.java:159)
> at
> org.apache.kafka.common.metrics.JmxReporter.metricChange(JmxReporter.java:77)
> at
> org.apache.kafka.common.metrics.Metrics.registerMetric(Metrics.java:288)
> at org.apache.kafka.common.metrics.Metrics.addMetric(Metrics.java:255)
> at org.apache.kafka.common.metrics.Metrics.addMetric(Metrics.java:239)
> at
> org.apache.kafka.clients.producer.internals.RecordAccumulator.registerMetrics(RecordAccumulator.java:137)
> at
> org.apache.kafka.clients.producer.internals.RecordAccumulator.<init>(RecordAccumulator.java:111)
> at
> org.apache.kafka.clients.producer.KafkaProducer.<init>(KafkaProducer.java:261)
> ... 9 more
> Caused by: javax.management.InstanceAlreadyExistsException:
> kafka.producer:type=producer-metrics,client-id=producer-3
> at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:437)
> at
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerWithRepository(DefaultMBeanServerInterceptor.java:1898)
> at
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:966)
> at
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:900)
> at
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:324)
> at
> com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:522)
> at
> org.apache.kafka.common.metrics.JmxReporter.reregister(JmxReporter.java:157)
> ... 16 more
> {noformat}
> I doubt that task in different taskslot of one taskmanager use different
> classloader， and taskid may be the same in one process。 So this lead to
> create kafkaProducer fail in one taskManager。
> Does anybody encountered the same problem？
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
