Pinging @elastic/es-distributed (Team:Distributed)

I would be inclined to do all the BroadcastResponse implementations at once

Are we sure none of the others generate a large response? The problem of moving to chunked by just wrapping a single chunk like that when the response is large, is that it will mean that we will serialize a large response on the transport thread where it was on whatever other thread it was on before. I'd rather be careful with that tbh.

Ah good point. Several of them are indeed quite large, and a little too complex to do them all at once I think. Could we introduce a ChunkedBroadcastResponse extends BaseBroadcastResponse implements ChunkedToXContent here since that's where I think we will eventually want to end up and it'll make the other moves a bit more mechanical?

here since that's where I think we will eventually want to end up and it'll make the other moves a bit more mechanical?

I just tried this. Currently this would cover IndicesStatsResponse and IndicesSegmentResponse. Both of these work somewhat differently in how they build the response, except for the header field. At least at this point forcing some abstraction onto this doesn't seem to get us much. Maybe try this again when moving the next one and it gets a little clearer what a nice version of this would be?

I just meant something like this: main...DaveCTurner:elasticsearch:2022-11-24-ChunkedBroadcastResponse-example

i.e. keep the header stuff in the base class and just add the custom stuff in the actual implementations.

Jup that's what I tried too, I guess I didn't really like how it adds extra chunks everywhere but meh maybe that's ok lets do it :)

@DaveCTurner I pushed a775d47 now and used it for the indices stats + existing segment stats.

Thanks both!