This is a follow-up to elastic#57573. This commit ensures that the bytes marked
in `WriteMemoryLimits` are released by any test using an internal test
cluster.

This is a follow-up to elastic#57573. This commit combines coordinating and
primary bytes under the same "write" bucket. Double accounting is
prevented by only accounting the bytes at either the reroute phase or
the primary phase. TransportBulkAction calls execute directly, so the
operations handler is skipped and the bytes are not double accounted.

This is a follow-up to #57573. This commit ensures that the bytes marked
in `WriteMemoryLimits` are released by any test using an internal test
cluster.

This is a follow-up to #57573. This commit combines coordinating and
primary bytes under the same "write" bucket. Double accounting is
prevented by only accounting the bytes at either the reroute phase or
the primary phase. TransportBulkAction calls execute directly, so the
operations handler is skipped and the bytes are not double accounted.

Currently we do not track the memory consuming by in-process write
operations.

This commit adds a mechanism to track write operation memory usage.

This is a follow-up to elastic#57573. This commit ensures that the bytes marked
in `WriteMemoryLimits` are released by any test using an internal test
cluster.

This is a follow-up to #57573. This commit ensures that the bytes marked
in WriteMemoryLimits are released by any test using an internal test
cluster.

This is a follow-up to elastic#57573. This commit combines coordinating and
primary bytes under the same "write" bucket. Double accounting is
prevented by only accounting the bytes at either the reroute phase or
the primary phase. TransportBulkAction calls execute directly, so the
operations handler is skipped and the bytes are not double accounted.

This is a follow-up to #57573. This commit combines coordinating and
primary bytes under the same "write" bucket. Double accounting is
prevented by only accounting the bytes at either the reroute phase or
the primary phase. TransportBulkAction calls execute directly, so the
operations handler is skipped and the bytes are not double accounted.

In elastic#57573 we introduced a `public static Logger logger` field in
`TransportChannel` which some IDEs tend to automatically import if you
mention an as-yet-undeclared `logger` field. This commit reverts that
small part of elastic#57573 so that we go back to using a private logger
belonging to `ChannelActionListener` instead.

In #57573 we introduced a `public static Logger logger` field in
`TransportChannel` which some IDEs tend to automatically import if you
mention an as-yet-undeclared `logger` field. This commit reverts that
small part of #57573 so that we go back to using a private logger
belonging to `ChannelActionListener` instead.