-
Notifications
You must be signed in to change notification settings - Fork 4
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
Seeing read limit exceeded error #75
Comments
Sorry we didn't notice this earlier. tl;dr: Add To avoid this error you need to up the When reading/parsing the influx requests the influx libraries used require a maximum number of bytes it will read from a network connection (as a general safety protection against DOS style attacks sending more data that a process can handle). Some clients are obviously sending more than the default of |
#81 now gives logging such as:
We'll leave this to run for a bit and then start to gather some stats for it. Eventually we'd like metrics/histograms for this info but we'll make do with scraping logs for now. Biggest so far I've seen in the hour since deployment is: That was quite easily over the original default of 100KB. |
|
We monitored our proxies for the largest batches seen coming from |
OK, going to close this in a couple of weeks (15th October 2023) if there's no further action. |
October? I meant 15th August 2023. |
I have telegraf writing about 100 points every 15 seconds and I'm seeing follow error:
level=info caller=errors.go:64 orgID=fake path=/api/v1/push/influx/write msg="problem reading body" response_code=400 err="read limit exceeded"
Any Idea what's going on?
The text was updated successfully, but these errors were encountered: