[ https://issues.apache.org/jira/browse/HBASE-7631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14273783#comment-14273783 ]
Jean-Daniel Cryans commented on HBASE-7631: ------------------------------------------- [~clehene] Things have changed a lot since then so I'm not sure what kind of work is required now. I'd close this unless someone is planning on working on it now that there's noise. > Region w/ few, fat reads was hard to find on a box carrying hundreds of > regions > ------------------------------------------------------------------------------- > > Key: HBASE-7631 > URL: https://issues.apache.org/jira/browse/HBASE-7631 > Project: HBase > Issue Type: Improvement > Components: metrics > Reporter: stack > > Of a sudden on a prod cluster, a table's rows gained girth... hundreds of > thousands of rows... and the application was pulling them all back every time > but only once a second or so. Regionserver was carrying hundreds of regions. > Was plain that there was lots of network out traffic. It was tough figuring > which region was the culprit (JD's trick was moving the regions off one at a > time while watching network out traffic on cluster to see whose spiked next > -- it worked but just some time). > If we had per region read/write sizes in metrics, that would have saved a > bunch of diagnostic time. -- This message was sent by Atlassian JIRA (v6.3.4#6332)