Circuit-break on response size #42318
Description
We have a circuit breaker for in_flight request but we don't check the response size even for APIs that can return big json output. For instance getting all _segments in a big cluster with lot of indices can kill the node responsible for the request since it needs to gather a lot of internal response as well as the final response that needs to be serialized in json. It could be beneficial to add a circuit breaker that checks the size of the transport responses when executing internal requests through the transport layer and to also control the memory usage of the response that is serialized at the rest layer. The latter is more important due to the json serialization that can be very verbose.