[KAFKA-14300] KRaft controller snapshot not trigger after resign

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.4.0, 3.3.2
• Assignee: José Armando García Sancio
• Reporter: José Armando García Sancio
• Created: 13/Oct/22 19:52
• Updated: 18/Oct/22 22:35
• Resolved: 18/Oct/22 22:35

Description

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.

Issue Links

• links to: GitHub Pull Request #12747