kafka-jira mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Randall Hauch (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (KAFKA-6279) Connect metrics do not get cleaned up for a source connector that doesn't stop properly
Date Tue, 28 Nov 2017 19:13:00 GMT

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

Randall Hauch updated KAFKA-6279:
---------------------------------
    Priority: Critical  (was: Major)

> Connect metrics do not get cleaned up for a source connector that doesn't stop properly
> ---------------------------------------------------------------------------------------
>
>                 Key: KAFKA-6279
>                 URL: https://issues.apache.org/jira/browse/KAFKA-6279
>             Project: Kafka
>          Issue Type: Bug
>          Components: KafkaConnect
>    Affects Versions: 1.0.0
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Critical
>
> Connect will call {{stop()}} on a source task to signal that it should "_stop trying
to poll for new data 
> and interrupt any outstanding poll() requests_" (see the [JavaDoc|http://kafka.apache.org/10/javadoc/org/apache/kafka/connect/source/SourceTask.html#stop--]
for this method).
> Unfortunately, not all connectors properly adhere to this expectation. Since the metrics
for the source task are cleaned up only when the worker source task's thread completes, a
task whose {{poll()}} method blocks forever will current prevent its thread from completing.
So, we need to change how the metrics are cleaned up to ensure this always happens.



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

Mime
View raw message