[
https://issues.apache.org/jira/browse/KAFKA-6504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16349545#comment-16349545
]
ASF GitHub Bot commented on KAFKA-6504:
---------------------------------------
rayokota opened a new pull request #4514: KAFKA-6504: Fix source task metric
caused by copy-paste error
URL: https://github.com/apache/kafka/pull/4514
This is a simple change to correct "sink-active-record-count" with
"source-active-record-count" for the
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> 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)
