Matthias J. Sax created KAFKA-21480:
---------------------------------------

             Summary: Kafka Streams might report "unknown lag" even if lag is 
zero
                 Key: KAFKA-21480
                 URL: https://issues.apache.org/jira/browse/KAFKA-21480
             Project: Kafka
          Issue Type: Bug
          Components: streams
    Affects Versions: 4.4.0
            Reporter: Matthias J. Sax
             Fix For: 4.5.0, 4.4.1


Affects new "streams" group only; does not apply to "classic" groups.

A standby task, and so a warm-up task, learnes the end offset of a changelog 
only from a restored batch. With nothing to restore -- an empty changelog, or 
local state already at the end of an idle changelog -- no batch ever arrives. 
The client then kept reporting an end offset of Long.MAX_VALUE for the task, 
which the broker reads as an unknown
lag. The warm-up task therefore never counted as caught up, and its migration 
stayed staged forever, holding a warm-up slot.



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

Reply via email to