Vincent Jiang created KAFKA-13717: ------------------------------------- Summary: KafkaConsumer.close throws authorization exception even when commit offsets is empty Key: KAFKA-13717 URL: https://issues.apache.org/jira/browse/KAFKA-13717 Project: Kafka Issue Type: Bug Components: unit tests Reporter: Vincent Jiang
When offsets is empty and coordinator is unknown, KafkaConsumer.close doesn't throw exception before commit [https://github.com/apache/kafka/commit/4b468a9d81f7380f7197a2a6b859c1b4dca84bd9|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. -- This message was sent by Atlassian Jira (v8.20.1#820001)