[KAFKA-16022] AsyncKafkaConsumer sometimes complains “No current assignment for partition {}”

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Done
• Affects Version/s: 3.7.0, 3.8.0, 3.7.1, 3.9.0
• Fix Version/s: 4.0.0
• Component/s: clients, consumer
• Labels: consumer-threading-refactor kip-848-client-support
• Assignee: Unassigned
• Reporter: Philip Nee
• Created: 16/Dec/23 05:09
• Updated: 15/Aug/24 14:10
• Resolved: 15/Aug/24 14:00

Description

This seems to be a timing issue that before the member receives any assignment from the coordinator, the fetcher will try to find the current position causing "No current assignment for partition {}".  This creates a small amount of noise to the log.

 

 

Issue Links

• is fixed by: KAFKA-16933 New consumer leave group flow may not send leave request and clear epoch
• is fixed by: KAFKA-16954 Move consumer leave operations on close to background thread
• is fixed by: KAFKA-17064 New consumer assign should update assignment in background thread
• is fixed by: KAFKA-17066 New consumer updateFetchPositions should perform all operations in background thread