Reduce default max content-length #67804
Labels
:Distributed/Network
Http and internode communication implementations
>enhancement
Team:Distributed
Meta label for distributed team
By default Elasticsearch supports a content-length of 100MB at the http layer. This default suggests that this is an appropriate size for bulk requests. 100MB is certainly much larger than necessary in order to achieve improved performance through reduced round trips and combined FSYNCs. Additionally, 100MB probably crosses the threshold, where performance is harmed due to the fact the content is not currently incrementally circuit broken and we probably do not handle that size of memory very effectively.
We should consider reducing this default to something more reasonable (8-32MB?). This is a static setting, so it would require clear release notes for 100MB users to reconfigure at rolling restart. Or it would need work to make it a dynamic setting (tricky).
The text was updated successfully, but these errors were encountered: