You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Renato Mefi (JIRA)" <ji...@apache.org> on 2018/12/31 08:57:00 UTC

[jira] [Commented] (KAFKA-7726) Connector status on deletion

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

Renato Mefi commented on KAFKA-7726:
------------------------------------

Are you running standalone or distributed mode? In the latter case I think this is the expected behavior since all the instances need some time to catch up with the latest configuration in the connect topics.

> Connector status on deletion
> ----------------------------
>
>                 Key: KAFKA-7726
>                 URL: https://issues.apache.org/jira/browse/KAFKA-7726
>             Project: Kafka
>          Issue Type: Bug
>          Components: KafkaConnect
>    Affects Versions: 1.1.0
>            Reporter: Eyal Ringort
>            Priority: Major
>
> When deleting a kafka-connect connector and then querying (via REST API - /connectors/connector-1234/status) for its status, response is not consistent - Sometimes we get:
> {code:java}
> HTTP/1.1 404 Not Found
> Content-Length: 88
> Content-Type: application/json
> Date: Wed, 12 Dec 2018 13:00:25 GMT
> Server: Jetty(9.2.24.v20180105)
> {
>     "error_code": 404,
>     "message": "No status found for connector connector-1234"
> }
> {code}
> And sometimes we get:
> {code:java}
> HTTP/1.1 200 OK
> Content-Length: 177
> Content-Type: application/json
> Date: Wed, 12 Dec 2018 13:00:06 GMT
> Server: Jetty(9.2.24.v20180105)
> {
>     "connector": {
>         "state": "UNASSIGNED",
>         "worker_id": "kafka:8083"
>     },
>     "name": "connector-1234",
>     "tasks": [
>         {
>             "id": 0,
>             "state": "RUNNING",
>             "worker_id": "kafka:8083"
>         }
>     ],
>     "type": "unknown"
> }
> {code}
> and after a while (can be a few seconds and up to a minute) we get the 404 response.
>  
> Plus, sometimes REST API calls to /connectors/ get stuck when the connector is in this "UNASSIGNED" status.
>  
> I'm using cp-kafka:4.1.2 & cp-kafka-connect:4.1.2



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