[KAFKA-13112] Controller's committed offset get out of sync with raft client listener context

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Fix Version/s: 3.0.0
• Component/s: controller, kraft
• Labels: kip-500
• Assignee: Jose Armando Garcia Sancio
• Reporter: Jose Armando Garcia Sancio
• Created: 21/Jul/21 02:06
• Updated: 02/Aug/21 14:12
• Resolved: 02/Aug/21 14:12

Description

The active controller creates an in-memory snapshot for every offset returned by RaftClient::scheduleAppend and RaftClient::scheduleAtomicAppend. For RaftClient::scheduleAppend, the RaftClient is free to split those records into multiple batches. Because of this when scheduleAppend is use there is no guarantee that the active leader will always have an in-memory snapshot for every "last committed offset".

To get around this problem, when the active controller renounces from leader if there is no snapshot at the last committed offset it will instead.

1. Reset the snapshot registry
2. Unregister the listener from the RaftClient
3. Register a new listener with the RaftClient

Sub-Tasks

• Add unregister support to the RaftClient.: Resolved
• Unregsiter listener during renounce when the in-memory snapshot is missing: Resolved