Skip to content

Conversation

@anubhav21sharma
Copy link

@anubhav21sharma anubhav21sharma commented Dec 24, 2025

Fixes 1204

Error message when originated from client-side:

MESSAGE_TOO_LARGE: The request included a message larger than the max message size the server will accept (uncompressed_bytes=100000500).

Error message when originated from broker-side:

MESSAGE_TOO_LARGE: The request included a message larger than the max message size the server will accept (uncompressed_bytes=100000513, compressed_bytes=5000045)

Copy link
Owner

@twmb twmb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

one comment - I think we can save a bool in the sink struct - but lgtm otherwise, let me know what you think, think you!

@anubhav21sharma
Copy link
Author

one comment - I think we can save a bool in the sink struct - but lgtm otherwise, let me know what you think, think you!

Fixed in f3a4de1. Thank you!

@anubhav21sharma anubhav21sharma force-pushed the feature-improve-message-too-large-error branch from f3a4de1 to 6c91ee4 Compare December 27, 2025 08:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Include the actual record size while returning MessageTooLarge error

2 participants