[
https://issues.apache.org/jira/browse/KAFKA-12262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17304256#comment-17304256
]
Randall Hauch commented on KAFKA-12262:
---------------------------------------
[https://github.com/apache/kafka/pull/10014] fixes this issue and KAFKA-12252.
> New session keys are never distributed when follower with key becomes leader
> ----------------------------------------------------------------------------
>
> Key: KAFKA-12262
> URL: https://issues.apache.org/jira/browse/KAFKA-12262
> Project: Kafka
> Issue Type: Bug
> Components: KafkaConnect
> Reporter: Chris Egerton
> Assignee: Chris Egerton
> Priority: Major
>
> The expiration time for session keys [starts at
> {{Long.MAX_VALUE}}|https://github.com/apache/kafka/blob/1c00d9dfa50570b4554a123bfe91ccc5e9ad1ca9/connect/runtime/src/main/java/org/apache/kafka/connect/runtime/distributed/DistributedHerder.java#L258]
> and [is updated when a new session key is read if and only if the worker is
> the
> leader|https://github.com/apache/kafka/blob/1c00d9dfa50570b4554a123bfe91ccc5e9ad1ca9/connect/runtime/src/main/java/org/apache/kafka/connect/runtime/distributed/DistributedHerder.java#L1579-L1581].
> If a follower reads a session key from the config topic, the expiration time
> will remain {{Long.MAX_VALUE}} and, even if the worker becomes the leader,
> will not be updated.
> Once this happens, all key rotation will cease until and unless the former
> leader of the cluster becomes the leader again without being restarted in the
> meantime, or all workers in the cluster are shut down at the same time and
> then the cluster is brought back up again.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
