kafka-jira mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Guozhang Wang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-5613) Deprecate JmxTool?
Date Mon, 05 Mar 2018 23:28:00 GMT

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

Guozhang Wang commented on KAFKA-5613:
--------------------------------------

I agree with KAFKA-5612 that for system tests we should consider using a different tool that
is race condition free; however deprecating it may not be a good idea since AFAIK lots of
users are using JMXTools for their monitoring purposes; and its popularity may even be comparable
to other OS eco-systems like Kafka Manager and Kafka Monitor.

Another use case that I can think of is to use JMXTool for some benchmarking.

> Deprecate JmxTool?
> ------------------
>
>                 Key: KAFKA-5613
>                 URL: https://issues.apache.org/jira/browse/KAFKA-5613
>             Project: Kafka
>          Issue Type: Bug
>    Affects Versions: 0.11.0.0
>            Reporter: Ewen Cheslack-Postava
>            Priority: Major
>
> According to git-blame, JmxTool has been around since October 2011. We use it in system
tests, but we are thinking it might be best to replace it: https://issues.apache.org/jira/browse/KAFKA-5612
> When making modifications for system tests, we've had to take into account compatibility
because this tool is technically included in our distribution and, perhaps unintentionally,
a public utility.
> We know that "real" tools for JMX, like jmxtrans, are more commonly used, but we don't
know who might be using JmxTool simply because it ships with Kafka. That said, it also isn't
documented in the Kafka documentation, so you probably have to dig around to find it.
> Hopefully we can deprecate this and eventually move it either to a jar that is only used
for system tests, or even better just remove it entirely. To do any of this, we'd probably
need to do at least a cursory survey of the community to get a feel for usage level.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message