org.apache.kafka.common.protocol.types.SchemaException: Error reading field 'topic_metadata': Error reading array of size 548723, only 36 bytes available


Solutions on the web

Solution icon of googlegroups
via Google Groups by Imran Akbar, 1 year ago
Error reading field 'topic_metadata': Error reading array of size 548723, only 36 bytes available

Solution icon of github
Error reading field 'topic_metadata': Error reading array of size 548723, only 74 bytes available

Solution icon of github
via GitHub by gitmahmud
, 1 year ago
Error reading field 'topic_metadata': Error reading array of size 1204063, only 1426 bytes available

Solution icon of googlegroups
via Google Groups by Unknown author, 10 months ago
Error reading field 'brokers': Error reading field 'host': Error reading string of length 26992, only 9805 bytes available

Solution icon of googlegroups
via Google Groups by PP, 3 months ago
Error reading field 'topic_metadata': Error reading array of size 548723, only 36 bytes available

Solution icon of github
Error reading field 'topic_metadata': Error reading array of size 423023, only 34 bytes available

Solution icon of stackoverflow
Error reading field 'topic_metadata': Error reading array of size 619631, only 37 bytes available

Solution icon of github
via GitHub by dmartindelorme
, 6 months ago
Error reading field 'topic_metadata': Error reading array of size 1936028205, only 40 bytes available

Solution icon of stackoverflow
Error reading field 'topic_metadata': Error reading array of size 873589, only 41 bytes available

Solution icon of googlegroups
Error reading field 'topics': Error reading array of size 1468532, only 28 bytes available

Stack trace

org.apache.kafka.common.protocol.types.SchemaException: Error reading 
 field 'topic_metadata': Error reading array of size 548723, only 36 bytes 
 available
	at org.apache.kafka.common.protocol.types.Schema.read(Schema.java:73)
	at org.apache.kafka.clients.NetworkClient.parseResponse(NetworkClient.java:380)
	at org.apache.kafka.clients.NetworkClient.handleCompletedReceives(NetworkClient.java:449)
	at org.apache.kafka.clients.NetworkClient.poll(NetworkClient.java:269)
	at org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient.clientPoll(ConsumerNetworkClient.java:360)
	at org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient.poll(ConsumerNetworkClient.java:224)
	at org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient.poll(ConsumerNetworkClient.java:178)
	at org.apache.kafka.clients.consumer.internals.Fetcher.getTopicMetadata(Fetcher.java:220)
	at org.apache.kafka.clients.consumer.KafkaConsumer.partitionsFor(KafkaConsumer.java:1270)
	at io.confluent.kafka.schemaregistry.storage.KafkaStoreReaderThread.<init>(KafkaStoreReaderThread.java:107)
	at io.confluent.kafka.schemaregistry.storage.KafkaStore.init(KafkaStore.java:154)
	at io.confluent.kafka.schemaregistry.storage.KafkaSchemaRegistry.init(KafkaSchemaRegistry.java:187)
	at io.confluent.kafka.schemaregistry.rest.SchemaRegistryRestApplication.setupResources(SchemaRegistryRestApplication.java:55)
	at io.confluent.kafka.schemaregistry.rest.SchemaRegistryRestApplication.setupResources(SchemaRegistryRestApplication.java:37)
	at io.confluent.rest.Application.createServer(Application.java:118)
	at io.confluent.kafka.schemaregistry.rest.SchemaRegistryMain.main(SchemaRegistryMain.java:43)

Write tip

You have a different solution? A short tip here would help you and many other users who saw this issue last week.

Users with the same issue

Samebug visitor profile picture
Unknown user
Once, 1 year ago
Samebug visitor profile picture
Unknown user
Once, 1 year ago
Samebug visitor profile picture
Unknown user
Once, 1 month ago
Once, 1 month ago
Samebug visitor profile picture
Unknown user
Once, 1 year ago
17 more bugmates