We should determine if there is a way to tracks metrics around replication coordinator mutex contention without taking too much of a performance hit. These metrics would have been useful for diagnosing recent cluster slowness issues more quickly, as the high mutex contention impacted read and write latency but it wasn't immediately obvious.

There is a possibility that this would be too costly, but we should investigate in this ticket.