More opinionated docs about http.max_content_length #90500
Conversation
Adds to the docs a note that the `100mb` default for `http.max_content_length` is the recommended maximum, along with suggestions for what to do when hitting this limit.
DaveCTurner
added
>docs
|
Documentation preview: |
elasticsearchmachine
added
Team:Distributed (Obsolete)
|
Pinging @elastic/es-docs (Team:Docs) |
|
Pinging @elastic/es-distributed (Team:Distributed) |
| When using the HTTP API, make sure that the client does not send HTTP chunks, | ||
| as this will slow things down. |
There was a problem hiding this comment.
I am not sure I understand the slow down of this and assume it is on purpose that you removed it. But curious if you found out why this is there (I see Clinton added it in 2013).
There was a problem hiding this comment.
Yes I'm also not sure where this came from and removing it was deliberate. Sending requests in chunks should actually be a little faster because it parallelises the accumulation of items in the bulk request with the sending of the request to ES. Even if it was slower in 2013 I don't think it's true today, or at least if it is then we should fix it rather than just documenting it.
💔 Backport failed
You can use sqren/backport to manually backport by running |
Adds to the docs a note that the `100mb` default for `http.max_content_length` is the recommended maximum, along with suggestions for what to do when hitting this limit.
3 participants
Adds to the docs a note that the
100mbdefault forhttp.max_content_lengthis the recommended maximum, along with suggestions for what to do when hitting this limit.