[KAFKA-13717] KafkaConsumer.close throws authorization exception even when commit offsets is empty

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.2.0
• Component/s: unit tests
• Assignee: Vincent Jiang
• Reporter: Vincent Jiang
• Created: 08/Mar/22 03:58
• Updated: 10/Mar/22 02:59
• Resolved: 10/Mar/22 02:59

Description

When offsets is empty and coordinator is unknown, KafkaConsumer.close doesn't throw exception before commit https://github.com/apache/kafka/commit/4b468a9d81f7380f7197a2a6b859c1b4dca84bd9.  After this commit, Kafka.close may throw authorization exception.

 

Root cause is because in the commit, the logic is changed to call lookupCoordinator even if offsets is empty. 

 

Even if a consumer doesn't have access to a group or a topic, it might be better to not throw authorization exception in this case because close() call doesn't touch actually access any resource.

Issue Links

• links to: GitHub Pull Request #11864