You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Arvid Heise (Jira)" <ji...@apache.org> on 2025/04/08 08:01:00 UTC

[jira] [Commented] (FLINK-32892) Handle Kafka clients JMX mBean errors by disabling JMX metrics

    [ https://issues.apache.org/jira/browse/FLINK-32892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17941811#comment-17941811 ] 

Arvid Heise commented on FLINK-32892:
-------------------------------------

Hi [~masc] / [~mason6345] ,

could you please clarify what you see and what you expect to happen?

Regarding the version, you need to prefix with kafka.

> Handle Kafka clients JMX mBean errors by disabling JMX metrics
> --------------------------------------------------------------
>
>                 Key: FLINK-32892
>                 URL: https://issues.apache.org/jira/browse/FLINK-32892
>             Project: Flink
>          Issue Type: Improvement
>          Components: Connectors / Kafka
>    Affects Versions: 1.17.1
>            Reporter: Mason Chen
>            Assignee: Mason Chen
>            Priority: Major
>             Fix For: kafka-4.0.0
>
>
> 3.4.x includes an implementation for KIP-830. [https://cwiki.apache.org/confluence/display/KAFKA/KIP-830%3A+Allow+disabling+JMX+Reporter]
> Many people on the mailing list have complained about confusing warning logs about mbean conflicts. We should be safe to disable this JMX reporter since Flink has its own metric system and the internal kafka-clients JMX reporter should not be used. 
> This affects Kafka connector release 3.1 and below (for some reason I cannot enter 3.1 in the affects version/s box).



--
This message was sent by Atlassian Jira
(v8.20.10#820010)