[
https://issues.apache.org/jira/browse/KAFKA-6504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Gustafson resolved KAFKA-6504.
------------------------------------
Resolution: Fixed
Fix Version/s: 1.1.0
> Connect: Some per-task-metrics not working
> ------------------------------------------
>
> Key: KAFKA-6504
> URL: https://issues.apache.org/jira/browse/KAFKA-6504
> Project: Kafka
> Issue Type: Bug
> Components: KafkaConnect
> Affects Versions: 1.0.0
> Reporter: Per Steffensen
> Assignee: Robert Yokota
> Priority: Minor
> Fix For: 1.1.0
>
>
> Some Kafka-Connect-metrics seems to be wrong with respect to per-task - at
> least it seems like MBean
> "kafka.connect:type=source-task-metrics,connector=<connector-name>,task=x"
> attribute "source-record-active-count" reports the same number for all x
> tasks running in the same Kafka-Connect instance/JVM. E.g. if I have a
> source-connector "my-connector" with 2 tasks that both run in the same
> Kafka-Connect instance, but I know that only one of them actually produces
> anything (and therefore can have "active source-records") both
> "kafka.connect:type=source-task-metrics,connector=my-connector,task=0" and
> "kafka.connect:type=source-task-metrics,connector=my-connector,task=1" goes
> up (following each other). It should only go up for the one task that
> actually produces something.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
