Alexey Zatelepin

> it seems like the timer could have been left in place to do optimistic fetching of metadata rather than in-lining the cost of refreshing metadata at the time of...

We investigated this one with @mmaslankaprv this morning - basically it is caused by stale health monitor data after a controller leader changed (partition balancer thought that partition sizes were...

should be fixed by #5922

As per the discussion with @mmaslankaprv this morning, `missing_node_rpc_client` error can be a consequence of the node trying to make an rpc request to itself. This can happen if the...

``` [DEBUG - 2022-08-09 03:07:42,301 - admin - _request - lineno:303]: Dispatching GET http://docker-rp-13:9644/v1/cluster/partition_balancer/status [WARNING - 2022-08-09 03:07:43,271 - admin - _request - lineno:321]: Response 500: {"message": "Unexpected error: rpc::errc::disconnected_endpoint(node...

BTW the test will be "fixed" once #5916 merges (admin server will return 503 which is a retryable error code).

Admin server will now return 503 and deeper rpc problems are tracked in #6005. Going to close.

@dotnwat found this issue by searching "could not parse header" I am seeing some strange rpc behavior as well in the following test run: https://github.com/redpanda-data/redpanda/issues/5471#issuecomment-1209505474 Basically there is a problem...

The same in [PartitionMoveInterruption.test_cancelling_partition_move_x_core](https://buildkite.com/redpanda/redpanda/builds/14195#0182a50d-85c6-4223-b5de-48577267f3f7)

one more https://buildkite.com/redpanda/redpanda/builds/14283#0182af58-13bd-411e-bd33-50cf3bd0764a