Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UNKNOWN_TOPIC_ID: This server does not host this topic ID #295

Closed
jrkinley opened this issue Dec 19, 2022 · 2 comments
Closed

UNKNOWN_TOPIC_ID: This server does not host this topic ID #295

jrkinley opened this issue Dec 19, 2022 · 2 comments

Comments

@jrkinley
Copy link

jrkinley commented Dec 19, 2022

I'm unable to consume from a topic created in Confluent Platform 7.2.1 due to UNKNOWN_TOPIC_ID errors. I'm using the latest version of franz-go (v.1.10.4).

Topic ID is a fairly recent change to the fetch protocol (KIP-516) and the latest version of franz-go includes a fix for handling unknown topic IDs, but it doesn't help in this case.

@jrkinley
Copy link
Author

After further investigation, this was actually caused by the setting inter.broker.protocol.version = 2.6, which resulted in the topic IDs not being reported by the API:

kcl metadata -t telemetry1
NAME        ID                                PARTITIONS  REPLICAS
telemetry1  00000000000000000000000000000000  1           1

Since topic IDs were added to the fetch request in Kafka v3.1.0 (KAFKA-10580) the workaround is to set the max version to v3.0.0:

kgo.NewClient(kgo.MaxVersions(kversion.V3_0_0()))

@twmb
Copy link
Owner

twmb commented Dec 22, 2022

I'll add a behavior improvement to not use v13 fetch requests if any topic does not have an ID. I'm not sure why Kafka would advertise v13 fetch requests for IBP 2.6, though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants