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

Posted to dev@kafka.apache.org by "José Armando García Sancio (Jira)" <ji...@apache.org> on 2022/10/13 19:53:00 UTC

[jira] [Created] (KAFKA-14300) KRaft controller snapshot not trigger after resign

José Armando García Sancio created KAFKA-14300:
--------------------------------------------------

             Summary: KRaft controller snapshot not trigger after resign
                 Key: KAFKA-14300
                 URL: https://issues.apache.org/jira/browse/KAFKA-14300
             Project: Kafka
          Issue Type: Bug
            Reporter: José Armando García Sancio
            Assignee: José Armando García Sancio


When the active KRaft controller resigns it resets the newBytesSinceLastSnapshot field to zero. This is not accurate since it is not guarantee that there is an on disk snapshot at the committed offset.

 

Since when the active controller resign it always reverts to the last committed state then it doesn't reset the newBytesSinceLastSnapshot. newBytesSinceLastSnapshot always represent committed bytes read since the last snapshot.



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