Make use of chunked REST response infrastructure in more APIs #89838
Description
Now that #88311 has landed and we have the infrastructure for serializing chunked REST responses, we should make use of it to fix the massive memory usage of APIs that are known to return large responses:
- snapshot status API (Chunked encoding for snapshot status API #90801)
- cluster state API (Chunked encoding for cluster state API #92285)
- get mappings API (Convert RestGetMappingAction to chunked encoding #89906)
- indices stats API (Use chunked encoding for indices stats response #91760)
- node stats API (Chunked Encoding for NodeStatsResponse #90097, Deeper chunking of node stats response #93985)
- field data stats (Chunked FieldUsageStatsResponse #91942)
- get indices API (Chunked encoding for RestGetIndicesAction #92034)
- index settings API (Use chunked encoding for RestGetSettingsAction #90326)
- search API Add Chunked rest encoding for Search APIs #95661
- _cat APIs (Chunked encoding for _cat APIs #92022)
- fields caps API (Make FieldCapabilitiesResponse use chunked encoding #89996)
- tasks API (Chunked encoding for tasks APIs #91935)
- pending cluster tasks API (Chunked encoding for pending tasks API #91929)
- recoveries API (Turn RecoveryResponse into a chunked REST response #89999)
- segments API (Make use of Chunked Encoding in the REST segments API #90136)
-
POST _cluster/reroute(includes the cluster state) (Chunked encoding for cluster reroute API #92615) - shard stores API (Simplify
IndicesShardStoresAction#94507) - cluster health API
- mget API