[
https://issues.apache.org/jira/browse/KAFKA-12474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17313476#comment-17313476
]
Randall Hauch commented on KAFKA-12474:
---------------------------------------
Merged to the `trunk` branch after the `2.8` branch was created and after code
freeze, and merged to:
* the `2.5` branch (for inclusion in upcoming 2.5.2),
* the `2.6` branch (for inclusion in upcoming 2.6.2),
* the `2.7` branch (for inclusion in upcoming 2.7.1),
* the `2.8` branch (for inclusion in upcoming 2.8.0) w/ permission from RM
> 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: Bug
> Components: KafkaConnect
> Affects Versions: 3.0.0, 2.4.2, 2.5.2, 2.8.0, 2.7.1, 2.6.2
> Reporter: Chris Egerton
> Assignee: Chris Egerton
> Priority: Major
> Fix For: 3.0.0, 2.5.2, 2.8.0, 2.7.1, 2.6.2
>
>
> 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)
