Hi Colin, Let's discuss this issue in KAFKA-13612 <https://issues.apache.org/jira/browse/KAFKA-13612> with Jason and Dom. (and anyone who is interested)
Thank you. Luke On Tue, Jan 25, 2022 at 2:43 AM Colin McCabe <cmcc...@apache.org> wrote: > Kafka internal topics are… well… internal, and we don’t guarantee anything > about their format or whether or not they are present, etc. There is no > guarantee that Kafka will always use __consumer-offsets to manage offsets — > it could change in the future. I think the big mistake we made is making > them visible to ordinary clients at all. > > So I would argue that this is not a regression since clients should not be > accessing internal topics. > > best, > Colin > > On Sun, Jan 23, 2022, at 13:50, Dominic Evans wrote: > > Luke Chen wrote: > >> Dominic Evans wrote: > >>> However, historically the __consumer_offsets topic was special cased > such > >>> that it would get auto-created on a Metadata request even if normal > topic > >>> auto-creation (`auto.create.topics.enable`) was disabled in the broker. > >>> Does anyone know if something has changed there? > >>> > >>> If I startup a brand new empty 2.8.x cluster and just send > >>> MetadataRequests for the __consumer_offsets topic I always get > >>> UNKNOWN_TOPIC_OR_PARTITION responses and the auto-creation doesn't > seem to > >>> ever get actioned for that alone. > > > >> Thanks for reporting the issue. Yes, I think this is a regression issue. > >> I've created a bug in JIRA: KAFKA-13612 > >> I'll work on a fix for it. > > > > Ah great, thanks Luke for confirming and also many thanks for raising > > the JIRA too. > > > > Best regards, > > Dom > > -- > > Dominic Evans > > IBM Software Group, Hursley Park, UK >
