[
https://issues.apache.org/jira/browse/KAFKA-14814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17703073#comment-17703073
]
Chaitanya Mukka commented on KAFKA-14814:
-----------------------------------------
Hi [~yash.mayya]! If you haven't started on this ticket would it be ok if I can
pick it up? This seems like a good starter ticket. I have a quick draft up here
- [https://github.com/apache/kafka/pull/13426]
> 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: Yash Mayya
> Priority: Minor
>
> 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)
