You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@kafka.apache.org by "Chris Egerton (Jira)" <ji...@apache.org> on 2023/03/23 15:25:00 UTC

[jira] [Resolved] (KAFKA-14814) Skip restart of connectors when redundant resume request is made

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

Chris Egerton resolved KAFKA-14814.
-----------------------------------
    Fix Version/s: 3.5.0
       Resolution: Fixed

> Skip restart of connectors when redundant resume request is made
> ----------------------------------------------------------------
>
>                 Key: KAFKA-14814
>                 URL: https://issues.apache.org/jira/browse/KAFKA-14814
>             Project: Kafka
>          Issue Type: Improvement
>          Components: KafkaConnect
>            Reporter: Chris Egerton
>            Assignee: Chaitanya Mukka
>            Priority: Minor
>             Fix For: 3.5.0
>
>
> Consecutive requests to the {{PUT /connectors/<name>/resume}} endpoint will cause the Connector to be restarted. This is a little wasteful and conflicts with the idempotent nature of that endpoint. We can tweak the {{MemoryConfigBackingStore}} and {{KafkaConfigBackingStore}} classes to not invoke the {{onConnectorTargetStateChange}} method of their {{ConfigUpdateListener}} instance if they pick up a new target state that matches the current target state of the connector.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)