Details
-
Improvement
-
Status: Closed
-
Minor
-
Resolution: Won't Fix
-
None
-
None
-
None
Description
It would be beneficial to have the "data transfer weight" of reads and writes per region server.
HBASE-3647 split out the read/write metric requests from the uber-"request" metric - which is great.
But there isn't a notion of "data transfer weight" and this is why it's important: the read metrics are effectively RPC-based. Thus, with a scan caching of 500, there is 1 RPC call every 500 rows read (and 1 'read' metric increment). And this metric doesn't indicate how much data is being transferred (e.g., a read with 50 attributes will probably cost a lot more than a read with 5 attributes).
Attachments
Issue Links
- is related to
-
HBASE-12911 Client-side metrics
- Closed