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

sarama.PacketDecodingError=kafka : error decoding packet: message of length 1213486160 too large or too small #1147

Closed
programmer4m opened this issue Aug 8, 2018 · 4 comments
Labels
stale Issues and pull requests without any recent activity Waiting for response

Comments

@programmer4m
Copy link

programmer4m commented Aug 8, 2018

Kafka Version:2.12
Go Version: 1.10.3

Problem Description

I find this in the log , no other issues found .
WARN kafka message: client/metadata got error from broker while fetching metadata:%!(EXTRA sarama.PacketDecodingError=kafka: error decoding packet: message of length 1213486160 too large or too small)

In detail log :

WARN kafka message: Initializing new client
WARN client/metadata fetching metadata for all topics from broker
WARN Connected to broker at ...... (unregistered)
WARN kafka message: client/metadata got error from broker while fetching metadata:%!(EXTRA sarama.PacketDecodingError=kafka: error decoding packet: message of length 1213486160 too large or too small)
WARN Closed connection to broker
WARN kafka message: client/metadata no available broker to send metadata request to
WARN client/brokers resurrecting 1 dead seed brokers

@wladh
Copy link
Contributor

wladh commented Aug 10, 2018

Might be a dup of #1144
There's no Kafka: 2.12, do you mean Kafka 2.0 compiled with Scala 2.12?

@d1egoaz d1egoaz changed the title sarama.PacketDecodingError=kafka : error decoding packet: message of length 1213486160 too large or too smal sarama.PacketDecodingError=kafka : error decoding packet: message of length 1213486160 too large or too small Aug 22, 2019
@d1egoaz
Copy link
Contributor

d1egoaz commented Aug 22, 2019

#1199 seems a dup of this

would this workaround work for you @programmer4m ?#1199 (comment)

@ghost
Copy link

ghost commented Feb 21, 2020

Thank you for taking the time to raise this issue. However, it has not had any activity on it in the past 90 days and will be closed in 30 days if no updates occur.
Please check if the master branch has already resolved the issue since it was raised. If you believe the issue is still valid and you would like input from the maintainers then please comment to ask for it to be reviewed.

@ghost ghost added the stale Issues and pull requests without any recent activity label Feb 21, 2020
@ghost ghost closed this as completed Mar 22, 2020
@lovasoa
Copy link

lovasoa commented Oct 15, 2020

  • 1213486160 is the decimal representation of 0x48 0x54 0x54 0x50 which is HTTP in ascii
  • What happened is probably this: A client expecting a binary payload (such as kafka) received an HTTP response instead. It may either be talking to the wrong host and port, or there is an HTTP proxy (such as kubernetes ingress) where there shouldn't be one.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale Issues and pull requests without any recent activity Waiting for response
Projects
None yet
Development

No branches or pull requests

4 participants