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

Make max_decoding_message_size configurable #609

Open
lxfind opened this issue Jan 9, 2025 · 1 comment
Open

Make max_decoding_message_size configurable #609

lxfind opened this issue Jan 9, 2025 · 1 comment
Labels
S-feature Severity: feature. This is adding a new feature.

Comments

@lxfind
Copy link

lxfind commented Jan 9, 2025

What problem are you trying to solve?

My application sends a large amount of data to tokio console and the default limit (4M) is too small.
It triggered the following error in tokio-console:

WARN tokio_console::conn: error from stream status=status: OutOfRange, message: "Error, decoded message length too large: found 206116357 bytes, the limit is: 4194304 bytes", details: [], metadata: MetadataMap { headers: {} }

How should the problem be solved?

It would be nice to be able to specify max_decoding_message_size in command line (or through env var) so that it works with large data. I can add it if this sounds like a good idea.

Any alternatives you've considered?

I don't think there is another way.

How would users interact with this feature?

example:

./tokio-console --max_decoding_message_size_mb 1024

Would you like to work on this feature?

yes

@lxfind lxfind added the S-feature Severity: feature. This is adding a new feature. label Jan 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S-feature Severity: feature. This is adding a new feature.
Projects
None yet
Development

No branches or pull requests

2 participants
@lxfind and others