How to debug - Message production error: MessageSizeTooLarge #17381
Unanswered
VitaliiNykyforov
asked this question in
Q&A
Replies: 1 comment 1 reply
-
It would be slow, but you could use a
To log messages where, when they are encoded as JSON, are bigger than N bytes. The length might not exactly match the Kafka message size (the encoding and event would need to be the same) but should hopefully help you find the large messages. A slight twist on this would be to use this in a |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
When the vector tries to send a message to Kafka we get an error like this:
Some(KafkaError (Message production error: MessageSizeTooLarge (Broker: Message size too large)))
I know how to fix this on kafka cluster side, but I want to debug this problem and understand which of the services trying to send so large massage. How I can catch this problem message? Thanks
PS. Before I tried to use /usr/bin/vector tap, but there are a lot of messages and difficult to identify it.
Beta Was this translation helpful? Give feedback.
All reactions