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 2021/03/16 03:28:00 UTC

[jira] [Created] (KAFKA-12474) Worker can die if unable to write new session key

Chris Egerton created KAFKA-12474:
-------------------------------------

             Summary: Worker can die if unable to write new session key
                 Key: KAFKA-12474
                 URL: https://issues.apache.org/jira/browse/KAFKA-12474
             Project: Kafka
          Issue Type: Improvement
          Components: KafkaConnect
    Affects Versions: 2.4.2, 2.5.2, 2.8.0, 2.7.1, 2.6.2
            Reporter: Chris Egerton
            Assignee: Chris Egerton


If a distributed worker is unable to write (and then read back) a new session key to the config topic, an uncaught exception will be thrown from its herder's tick thread, killing the worker.

See [https://github.com/apache/kafka/blob/8da65936d7fc53d24c665c0d01893d25a430933b/connect/runtime/src/main/java/org/apache/kafka/connect/runtime/distributed/DistributedHerder.java#L366-L369]

One way we can handle this case by forcing a read to the end of the config topic whenever an attempt to write a new session key to the config topic fails.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)