KV bytes read is incorrectly reported as 0:

The problem is that we are eagerly closing the cFetcher which nils out row.KVFetcher, and the latter is responsible for reporting the number of bytes read. The bug is present on master and probably on 21.2.