[ https://issues.apache.org/jira/browse/KAFKA-6504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16355089#comment-16355089 ]
Per Steffensen commented on KAFKA-6504: --------------------------------------- Havnt looked that much into the patch from PR 4514, but do you expect that it fixes the problem? Besides tests, the only thing it does is to change a metric name from sink-record-active-count to source-record-active-count. But where was source-record-active-count then controlled before? Please note that my observation is not that source-record-active-count did not exist or was always 0. The observed problem was/is that it seemed to be the same value for all tasks, and that it was increasing for all tasks, even if there were only activity in one task. > 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 > Priority: Minor > > 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)