kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ismael Juma (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (KAFKA-4946) Evaluation of kafka_mx4jenable is inverted
Date Tue, 03 Oct 2017 10:29:01 GMT

     [ https://issues.apache.org/jira/browse/KAFKA-4946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Ismael Juma resolved KAFKA-4946.
--------------------------------
    Resolution: Duplicate

Marking as duplicate of KAFKA-5843 as that had a PR. Credited Ralph as well in the merged
commit:

https://github.com/apache/kafka/commit/716330a5b2f629e6bb0316b5f036837660916a0e

> Evaluation of kafka_mx4jenable is inverted
> ------------------------------------------
>
>                 Key: KAFKA-4946
>                 URL: https://issues.apache.org/jira/browse/KAFKA-4946
>             Project: Kafka
>          Issue Type: Bug
>          Components: core, metrics
>    Affects Versions: 0.10.2.0
>            Reporter: Ralph Weires
>            Priority: Minor
>         Attachments: mx4j-enable.patch
>
>
> Mx4j stopped working for me after upgrade from 0.8.2 -> 0.10.2.0
> I had the "-Dkafka_mx4jenable=true" flag set in a custom start script, which however
now actually prevents MX4J from being loaded in 0.10.2.0
> The flag is only taken into account since the patch from KAFKA-2002 it seems to me -
we should however skip trying to load MX4J if the flag is set to false, rather than if it's
set to true (as it's currently done).
> Trivial patch attached, check should be negated.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message