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

Posted to jira@kafka.apache.org by "Spacrocket (Jira)" <ji...@apache.org> on 2024/09/30 22:02:00 UTC

[jira] (KAFKA-17627) ConfigProvider TTLs do not restart Tasks

    [ https://issues.apache.org/jira/browse/KAFKA-17627 ]


    Spacrocket deleted comment on KAFKA-17627:
    ------------------------------------

was (Author: JIRAUSER289157):
Hi, [~gharris1727] I'd like to help with this one. I've assigned it to me :)

> ConfigProvider TTLs do not restart Tasks
> ----------------------------------------
>
>                 Key: KAFKA-17627
>                 URL: https://issues.apache.org/jira/browse/KAFKA-17627
>             Project: Kafka
>          Issue Type: Bug
>          Components: connect
>    Affects Versions: 2.0.0
>            Reporter: Greg Harris
>            Assignee: Spacrocket
>            Priority: Major
>              Labels: newbie
>
> The ConfigProvider interface allows for implementations to provide configurations with an accompanying Time To Live, a lifetime that the returned value is valid for. Callers which receive a TTL should periodically call the ConfigProvider to refresh and receive any updated value.
> The WorkerConfigTransformer is responsible for accepting TTLs from ConfigProviders, and scheduling restarts for connectors to force them to refresh their externalized configurations.
> Since the introduction of the ConfigProvider interface in 2.0.0, when the WorkerConfigTransformer processes task configurations, it schedules a restart of the connector, which may or may not be present on the running machine. Instead, when secrets for a task include a TTL, the task should be restarted directly.



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